diff --git a/_pages/manage/2018-05-25-manage-pmr.md b/_pages/manage/2018-05-25-manage-pmr.md index 8061ac417..4d15aedca 100644 --- a/_pages/manage/2018-05-25-manage-pmr.md +++ b/_pages/manage/2018-05-25-manage-pmr.md @@ -48,30 +48,30 @@ In a Spring 2023 Section 508 Program Maturity Report - Executive Summary (PDF) -* Spring 2023 Section 508 Program Maturity Report - Executive Supplemental (PDF) +* Spring 2023 Section 508 Program Maturity Report - Executive Summary (PDF) +* Spring 2023 Section 508 Program Maturity Report - Executive Supplemental (PDF) ### 2022 -* Autumn 2022 Section 508 Program Maturity Report - Executive Summary (PDF) -* Autumn 2022 Section 508 Program Maturity Report - Executive Supplemental (PDF) -* Spring 2022 Section 508 Program Maturity Report - Executive Summary (PDF) -* Spring 2022 Section 508 Program Maturity Report - Executive Supplemental (PDF) +* Autumn 2022 Section 508 Program Maturity Report - Executive Summary (PDF) +* Autumn 2022 Section 508 Program Maturity Report - Executive Supplemental (PDF) +* Spring 2022 Section 508 Program Maturity Report - Executive Summary (PDF) +* Spring 2022 Section 508 Program Maturity Report - Executive Supplemental (PDF) ### 2021 -* Autumn 2021 Section 508 Program Maturity Report - Executive Summary (PDF) -* Autumn 2021 Section 508 Program Maturity Report - Executive Supplemental (PDF) -* Spring 2021 Section 508 Program Maturity Report - Executive Summary (PDF) -* Spring 2021 Section 508 Program Maturity Report - Executive Supplemental (PDF) +* Autumn 2021 Section 508 Program Maturity Report - Executive Summary (PDF) +* Autumn 2021 Section 508 Program Maturity Report - Executive Supplemental (PDF) +* Spring 2021 Section 508 Program Maturity Report - Executive Summary (PDF) +* Spring 2021 Section 508 Program Maturity Report - Executive Supplemental (PDF) ### 2020 -* Autumn 2020 Section 508 Program Maturity Report - Executive Summary (PDF) -* Autumn 2020 Section 508 Program Maturity Report - Executive Supplemental (PDF) -* Spring 2020 Section 508 Program Maturity Report - Executive Summary (PDF) -* Spring 2020 Section 508 Program Maturity Report - Executive Supplemental (PDF) +* Autumn 2020 Section 508 Program Maturity Report - Executive Summary (PDF) +* Autumn 2020 Section 508 Program Maturity Report - Executive Supplemental (PDF) +* Spring 2020 Section 508 Program Maturity Report - Executive Summary (PDF) +* Spring 2020 Section 508 Program Maturity Report - Executive Supplemental (PDF) ### 2019 -* Autumn 2019 Section 508 Program Maturity Report - Executive Summary (PDF) -* Spring 2019 Section 508 Program Maturity Report - Executive Summary (PDF) +* Autumn 2019 Section 508 Program Maturity Report - Executive Summary (PDF) +* Spring 2019 Section 508 Program Maturity Report - Executive Summary (PDF)

Understanding the Reporting Questions

diff --git a/_pages/manage/annual-assessment/2023-12-13-manage-gwaa-annual-reports.md b/_pages/manage/annual-assessment/2023-12-13-manage-gwaa-annual-reports.md index 24635075a..dfbc33510 100644 --- a/_pages/manage/annual-assessment/2023-12-13-manage-gwaa-annual-reports.md +++ b/_pages/manage/annual-assessment/2023-12-13-manage-gwaa-annual-reports.md @@ -25,13 +25,13 @@ Annual assessment reports are made available on this website in HTML or as a dow
- FY 24 Governmentwide Section 508 Assessment Report Cover + FY 24 Governmentwide Section 508 Assessment Report Cover

FY 24 Governmentwide Section 508 Assessment

Submitted to Congress and published on December 19, 2024

@@ -42,13 +42,13 @@ Annual assessment reports are made available on this website in HTML or as a dow
- FY 23 Governmentwide Section 508 Assessment Report Cover + FY 23 Governmentwide Section 508 Assessment Report Cover

FY 23 Governmentwide Section 508 Assessment

Submitted to Congress and published on December 29, 2023

diff --git a/_pages/manage/annual-assessment/2023-report/2023-appx-d-entity-summary-report.html b/_pages/manage/annual-assessment/2023-report/2023-appx-d-entity-summary-report.html index 93395a9ff..2079b1cb3 100644 --- a/_pages/manage/annual-assessment/2023-report/2023-appx-d-entity-summary-report.html +++ b/_pages/manage/annual-assessment/2023-report/2023-appx-d-entity-summary-report.html @@ -21,7 +21,7 @@
- Placeholder image + Placeholder image
@@ -41,7 +41,7 @@

- +
@@ -291,7 +291,7 @@

Maturity Outcomes

if (entity_data[i].id === id) { //Entity logo/seal and alt text if (entity_data[i].seal == "") { - document.getElementById("entity-seal").setAttribute("src", "https://assets.section508.gov/files/reports/cr-2023/image-placeholder.png"); + document.getElementById("entity-seal").setAttribute("src", "https://assets.section508.gov/assets/images/assessment/fy23/image-placeholder.png"); } else { const altTextSeal = "Logo of " + entity_data[i].name; document.getElementById("entity-seal").setAttribute("src", entity_data[i].seal); diff --git a/_pages/manage/annual-assessment/2023-report/2023-assessment-data.md b/_pages/manage/annual-assessment/2023-report/2023-assessment-data.md index 836832524..842bda965 100644 --- a/_pages/manage/annual-assessment/2023-report/2023-assessment-data.md +++ b/_pages/manage/annual-assessment/2023-report/2023-assessment-data.md @@ -22,12 +22,12 @@ format: "HTML (html)" To enhance the transparency of this report and respondent data, we have made them publicly available as an open government data asset. You can find downloadable content related to the FY 23 Governmentwide Section 508 Assessment below, which includes: diff --git a/_pages/manage/annual-assessment/2023-report/2023-findings-acquisition.md b/_pages/manage/annual-assessment/2023-report/2023-findings-acquisition.md index 6b7828c00..6f5a741a2 100644 --- a/_pages/manage/annual-assessment/2023-report/2023-findings-acquisition.md +++ b/_pages/manage/annual-assessment/2023-report/2023-findings-acquisition.md @@ -20,7 +20,7 @@ Including ICT accessibility requirements during procurement and ensuring that ve Of the 231 reporting entities who release solicitations, the majority of respondents who release solicitations (169 reporting entities or 73%) said ICT accessibility requirements are regularly, frequently, or almost always included in solicitations, with the remaining 25% of reporting entities noting ad hoc or no inclusion of ICT accessibility requirements.25 However, of the 241 reporting entities who award contracts, the majority of respondents (127 reporting entities or 53%) said they are inconsistent in verifying Section 508 conformance, often doing so on an ad hoc basis or not at all.26 Figure 21 depicts the full breakdown, with only 39 reporting entities (16%) almost always verifying contract deliverables prior to acceptance. Additionally, 140 reporting entities (63%) indicated their quality assurance activities do not or only sometimes include actions to address vendors and contractors who produce or deliver non-conformant ICT despite agreed-to contractual requirements to conform to Section 508 standards.27 This indicates a significant gap in ensuring Section 508 compliance of contract deliverables prior to acceptance despite the deliverables requiring Section 508 conformance.
-
A bar graph shows the count of responses according to approach to verifying contract deliverables that are required to be Section 508 conformant (Q55): 28 respondents selected "no method is implemented for verifying contract deliverables"; 99 selected "contract deliverables are only sometimes verified"; 54 selected "contract deliverables are regularly verified"; 21 selected "contract deliverables are frequently verified"; 39 selected "contract deliverables are almost always verified"; and 8 selected "N/A - does not award contracts". +
A bar graph shows the count of responses according to approach to verifying contract deliverables that are required to be Section 508 conformant (Q55): 28 respondents selected "no method is implemented for verifying contract deliverables"; 99 selected "contract deliverables are only sometimes verified"; 54 selected "contract deliverables are regularly verified"; 21 selected "contract deliverables are frequently verified"; 39 selected "contract deliverables are almost always verified"; and 8 selected "N/A - does not award contracts".
Figure 21. Response count of approaches to verifying contract deliverables that are required to be Section 508 conformant (Q55)
@@ -44,7 +44,7 @@ Additionally, reporting entities include users with disabilities at varying leve * 23 respondents (6%) selected other.
-
A donut chart shows percentage of responses indicating ways in which users with disabilities are included in acquisition and development of ICT were: 40% of respondents selected "Ad hoc/informal"; 10% selected "disabilities are included in customer/user personas"; 10% selected "individuals with disabilities are consulted when defining customer/user needs"; 8% selected "individuals with disabilities are consulted in development of Section 508 conformance validation testing processes"; 8% selected "individuals with disabilities are directly involved in Section 508 conformance validation testing"; 8% selected "individuals with disabilities are directly involved in user acceptance testing;" 10% selected "none"; and 6% selected "other". +
A donut chart shows percentage of responses indicating ways in which users with disabilities are included in acquisition and development of ICT were: 40% of respondents selected "Ad hoc/informal"; 10% selected "disabilities are included in customer/user personas"; 10% selected "individuals with disabilities are consulted when defining customer/user needs"; 8% selected "individuals with disabilities are consulted in development of Section 508 conformance validation testing processes"; 8% selected "individuals with disabilities are directly involved in Section 508 conformance validation testing"; 8% selected "individuals with disabilities are directly involved in user acceptance testing;" 10% selected "none"; and 6% selected "other".
Figure 22. Percentages of responses indicating ways in which users with disabilities are included in acquisition and development of ICT (Q6)
@@ -64,7 +64,7 @@ When asked to indicate how the needs of individuals with disabilities are includ * 15 respondents (6%) selected N/A - does not generate business needs or participate in acquisition planning processes or equivalent.
-
A bar graph shows the percentage of responses for inclusion of PWD during the assessment of ICT-related business needs or equivalent acquisition planning processes (Q56): 13% of respondents selected "the needs of individuals with disabilities are not deliberately considered when determining business needs in ICT acquisitions"; 44% selected "business needs sometimes consider/include needs of individuals with disabilities but generally on an ad hoc basis (some consideration for user needs, some determination of applicable Section 508 standards, some determination of exception/exemption)"; 17% selected "the needs of individuals with disabilities are deliberately defined as part of the business needs assessment, or equivalent, and are regularly considered/included in ICT acquisitions"; 10% selected "the needs of individuals with disabilities are deliberately defined as part of the business needs assessment, or equivalent, and are frequently considered/included"; 10% selected "the needs of individuals with disabilities are integrated into business needs processes, or equivalent, almost always included, and feedback loops are established for  continuous refinement"; and 6% selected "N/A - does not generate business needs or participate in acquisition planning processes or equivalent". +
A bar graph shows the percentage of responses for inclusion of PWD during the assessment of ICT-related business needs or equivalent acquisition planning processes (Q56): 13% of respondents selected "the needs of individuals with disabilities are not deliberately considered when determining business needs in ICT acquisitions"; 44% selected "business needs sometimes consider/include needs of individuals with disabilities but generally on an ad hoc basis (some consideration for user needs, some determination of applicable Section 508 standards, some determination of exception/exemption)"; 17% selected "the needs of individuals with disabilities are deliberately defined as part of the business needs assessment, or equivalent, and are regularly considered/included in ICT acquisitions"; 10% selected "the needs of individuals with disabilities are deliberately defined as part of the business needs assessment, or equivalent, and are frequently considered/included"; 10% selected "the needs of individuals with disabilities are integrated into business needs processes, or equivalent, almost always included, and feedback loops are established for  continuous refinement"; and 6% selected "N/A - does not generate business needs or participate in acquisition planning processes or equivalent".
Figure 23. Percentage of responses for inclusion of PWD during the assessment of ICT-related business needs or equivalent acquisition planning process (Q56)
diff --git a/_pages/manage/annual-assessment/2023-report/2023-findings-complaints.md b/_pages/manage/annual-assessment/2023-report/2023-findings-complaints.md index 39a7fec8a..c66405c08 100644 --- a/_pages/manage/annual-assessment/2023-report/2023-findings-complaints.md +++ b/_pages/manage/annual-assessment/2023-report/2023-findings-complaints.md @@ -20,7 +20,7 @@ Procuring and using non-conformant ICT can expose reporting entities to Section The majority of reporting entities (131 reporting entities or 53% ) reported providing instructions about how the public and employees can file complaints related to Section 508. Conversely, as depicted in Figure 24, 110 reporting entities (44%) said they lack formal, written policies and procedures for processing and resolving complaints filed in relation to Section 508 non-conformance issues. This breaks down to 40 reporting entities (16%) that have no established policies, procedures, or processes, 51 reporting entities (20%) that manage Section 508-related complaints only on an ad hoc basis but have a plan to establish formal policies and procedures, and 19 reporting entities (8%) that did not know the status of a policy, procedure or process for handling Section 508 complaints.
-
A bar graph shows the count of responses indicating formal, written policies and procedures for processing and resolving complaints filed in relation to Section 508 non-conformance issues Q29): 40 respondents selected no, responding entity has not established any policies or procedures to process Section 508-related complaints; 51 selected responding entity manages Section 508-related complaints on an ad hoc basis and has a plan to establish formal policies and procedures for processing and resolving complaints specifically related to Section 508 non-conformance; 98 selected responding entity has a formally established complaint process with specific procedures for dealing with Section 508-related complaints; 17 selected responding entity has established specific, repeatable policies and/or procedures to process Section 508-related complaints and has established performance measures related to processing Section 508-related complaints; 24 selected responding entity has established specific policies and/or procedures to process Section 508-related complaints with a tracking system and feedback loops for continuous improvement; and 19 selected Unknown. +
A bar graph shows the count of responses indicating formal, written policies and procedures for processing and resolving complaints filed in relation to Section 508 non-conformance issues Q29): 40 respondents selected no, responding entity has not established any policies or procedures to process Section 508-related complaints; 51 selected responding entity manages Section 508-related complaints on an ad hoc basis and has a plan to establish formal policies and procedures for processing and resolving complaints specifically related to Section 508 non-conformance; 98 selected responding entity has a formally established complaint process with specific procedures for dealing with Section 508-related complaints; 17 selected responding entity has established specific, repeatable policies and/or procedures to process Section 508-related complaints and has established performance measures related to processing Section 508-related complaints; 24 selected responding entity has established specific policies and/or procedures to process Section 508-related complaints with a tracking system and feedback loops for continuous improvement; and 19 selected Unknown.
Figure 24. Response count indicating formal, written policies and procedures for processing and resolving complaints filed in relation to Section 508 non-conformance issues (Q29)
diff --git a/_pages/manage/annual-assessment/2023-report/2023-findings-dimension.md b/_pages/manage/annual-assessment/2023-report/2023-findings-dimension.md index 2378e5cc6..8cc92f2d9 100644 --- a/_pages/manage/annual-assessment/2023-report/2023-findings-dimension.md +++ b/_pages/manage/annual-assessment/2023-report/2023-findings-dimension.md @@ -42,7 +42,7 @@ Maturity questions ranged from Q22 to Q61 (excepting Q27B) (See -
A bar graph shows the average maturity dimension ratings across all reporting entities: 2.27 for IT Accessibility Program Office, 2.54 for Policies, Procedures, and Practices, 2.10 for Communications, 2.34 for Content Creation, 1.63 for Human Capital, Culture, and Leadership, 2.57 for Technology Lifecycle Activities, 2.04 for Testing and Validation, 2.44 for Acquisitions and Procurement, and 1.57 for Training. +
A bar graph shows the average maturity dimension ratings across all reporting entities: 2.27 for IT Accessibility Program Office, 2.54 for Policies, Procedures, and Practices, 2.10 for Communications, 2.34 for Content Creation, 1.63 for Human Capital, Culture, and Leadership, 2.57 for Technology Lifecycle Activities, 2.04 for Testing and Validation, 2.44 for Acquisitions and Procurement, and 1.57 for Training.
Figure 5. Average maturity dimension ratings across all reporting entities
@@ -61,27 +61,27 @@ Some additional descriptive statistics around the maturity dimensions include:
- +
- +
-
A donut chart shows the percentage of reporting entities with Human Capital, Culture, and Leadership as their lowest dimension: 35%. All others: 65%. +
A donut chart shows the percentage of reporting entities with Human Capital, Culture, and Leadership as their lowest dimension: 35%. All others: 65%.
Figure 7. Percentage of reporting entities with Human Capital, Culture, and Leadership as their lowest maturity dimension (86 of 249 reporting entities)
- +
-
A donut chart shows the percentage of reporting entities with Policies, Procedures and Standards as their highest dimension: 25%. All others: 75%. +
A donut chart shows the percentage of reporting entities with Policies, Procedures and Standards as their highest dimension: 25%. All others: 75%.
Figure 8. Percentage of reporting entities with Policies, Procedures, and Standards as their highest maturity dimension (63 of 249 reporting entities)
@@ -89,7 +89,7 @@ Some additional descriptive statistics around the maturity dimensions include:
-
A donut chart shows the percentage of reporting entities with Technology Lifecycle Activities as their highest dimension: 20%. All others: 80%. +
A donut chart shows the percentage of reporting entities with Technology Lifecycle Activities as their highest dimension: 20%. All others: 80%.
Figure 9. Percentage of reporting entities with Technology Lifecycle Activities as their highest maturity dimension (50 of 249 reporting entities)
diff --git a/_pages/manage/annual-assessment/2023-report/2023-findings-key-compliance.md b/_pages/manage/annual-assessment/2023-report/2023-findings-key-compliance.md index cc3af246b..439557099 100644 --- a/_pages/manage/annual-assessment/2023-report/2023-findings-key-compliance.md +++ b/_pages/manage/annual-assessment/2023-report/2023-findings-key-compliance.md @@ -47,7 +47,7 @@ The Assessment asked respondents to report on Section 508 web page testing perfo
-
Responses for requested ICT testing: For Top Intranet: 37% submitted test results, 55% selected unavailable, no resources to test, and 9% selected N/A.  For top internet: 48% submitted test results, 51% selected unavailable, no resources to test, and 1% selected N/A. For top electronic documents, 41% submitted test results, 57% selected unavailable, no resources to test, and 2% selected N/A. For top videos, 35% submitted results, 55% selected unavailable, no resources to test and 10% selected N/A. +
Responses for requested ICT testing: For Top Intranet: 37% submitted test results, 55% selected unavailable, no resources to test, and 9% selected N/A.  For top internet: 48% submitted test results, 51% selected unavailable, no resources to test, and 1% selected N/A. For top electronic documents, 41% submitted test results, 57% selected unavailable, no resources to test, and 2% selected N/A. For top videos, 35% submitted results, 55% selected unavailable, no resources to test and 10% selected N/A.
Figure 1. Percentage of respondents submitting conformance testing results for the top intranet and internet web pages, electronic documents, and videos (Q78 to Q81)
@@ -58,7 +58,7 @@ Respondents reported relying heavily on only automated accessibility testing too With heavy reliance on solely automated testing for public web pages, there is risk of inflation of conformance scores due to the inability of automated tools to comprehensively test for all Section 508 requirements. Automated testing omits of over half of the Section 508 requirements, and fewer requirements tested means fewer chances for failure. However, reporting entities’ data nevertheless indicate similar levels of conformance with intranet pages, which tend to incorporate more manual inspection along with automated testing. Our speculated reasons for the similar conformance level patterns include:
-
25% of top intranet pages were reported as fully conformant. 22% of internet pages were reported as fully conformant. 21% of top electronic documents were reported as fully conformant. 29% of top videos were reported as fully conformant. +
25% of top intranet pages were reported as fully conformant. 22% of internet pages were reported as fully conformant. 21% of top electronic documents were reported as fully conformant. 29% of top videos were reported as fully conformant.
Figure 2. Percentage of fully conformant ICT for all top intranet web pages, internet web pages, electronic documents, and videos tested (Q78 to Q81)
@@ -149,7 +149,7 @@ Within the reporting period, respondents were asked to identify and test the top The criteria included questions on if specific federal organization's ICT, including public or internal use, fully conformed to Section 508 standards. Although 100% conformance is the standard, the highest percent conformant ICT was enterprise email applications reported to be at about 62% conformant across government. The least conformant widely-used ICT included in the Assessment was W2s at just over 31%. Out of the 97 reporting entities who reported having custom developed desktop software or native mobile applications used by the public, only 23% reported fully conformant ICT. Additionally, out of the 24 reporting entities who reported having kiosks used by the public, only 46% reported fully conformant kiosks. Figure 3 shows the percentage of additional ICT that fully conform to Section 508 standards and Table 1 details responses for conformance of ICT from the Assessment criteria.
-
Percentage of agencies reporting full conformance for select ICT: 31.7% fully conformed for Time and Attendance; 62.2% for Email App; 57.8% Virtual Meeting Platform, 51.4% Telework Agreement, 49.0% for SSO technology, 31.3% for W2, and 51% for employee training. +
Percentage of agencies reporting full conformance for select ICT: 31.7% fully conformed for Time and Attendance; 62.2% for Email App; 57.8% Virtual Meeting Platform, 51.4% Telework Agreement, 49.0% for SSO technology, 31.3% for W2, and 51% for employee training.
Figure 3. Percentage of reporting entities noting full conformance by products used internally and by the public (Q82 to Q85, Q89 to Q92, respectively)
@@ -273,7 +273,7 @@ To comprehensively and quantitatively assess Section 508 compliance across the f As Figure 4 below depicts, reporting entities fall across the scale from zero to five on both axes, with a heavy concentration of reporting entities located in the bottom and left of the graph. The red trend line shows an upward trend, indicating that generally, as a reporting entity’s maturity increased, their conformance also tended to increase. Thus, reporting entities with greater capacity to execute activities related to accessibility, such as testing or training, tended to have more conformant ICT products.
-
A scatter plot shows the distribution of agencies on a 0-to-5 scale across the x-axis representing maturity (m-index) and the y-axis representing conformance (c-index), with a heavy concentration of respondents located in the bottom and left of the graph. A dark red trend line shows an upward trend, indicating that, as respondent’s maturity increased, their conformance also generally tended to increase. Table 3 further details the number of respondents who fell into specific brackets. +
A scatter plot shows the distribution of agencies on a 0-to-5 scale across the x-axis representing maturity (m-index) and the y-axis representing conformance (c-index), with a heavy concentration of respondents located in the bottom and left of the graph. A dark red trend line shows an upward trend, indicating that, as respondent’s maturity increased, their conformance also generally tended to increase. Table 3 further details the number of respondents who fell into specific brackets.
Figure 4. Percentage of respondents submitting conformance testing results for the top intranet and internet web pages, electronic documents, and videos (Q78 to Q81)
diff --git a/_pages/manage/annual-assessment/2023-report/2023-findings-program-staff.md b/_pages/manage/annual-assessment/2023-report/2023-findings-program-staff.md index 8e6c2f132..4ad1c6fc6 100644 --- a/_pages/manage/annual-assessment/2023-report/2023-findings-program-staff.md +++ b/_pages/manage/annual-assessment/2023-report/2023-findings-program-staff.md @@ -37,7 +37,7 @@ format: "HTML (html)"
-
A bar chart showing the percentages of governmentwide Section 508 PM or equivalent utilization Q3): 28.1% of reporting entities had a full-time Section 508 PM, 51.4% had a part-time Section 508 PM, and 20.5% had no Section 508 PM. +
A bar chart showing the percentages of governmentwide Section 508 PM or equivalent utilization Q3): 28.1% of reporting entities had a full-time Section 508 PM, 51.4% had a part-time Section 508 PM, and 20.5% had no Section 508 PM.
Figure 10. Percentages of governmentwide Section 508 PM or equivalent utilization (Q3)
@@ -89,13 +89,13 @@ Table 4 depicts the average hours per week Section 508 PMs dedicate to their Sec
-
A line graph shows that, as the maturity bracket increases, the average total FTE increases: The line graph data shows: 0.2 FTEs in the Very Low bracket, 2.5 FTEs in the Low bracket, 5.3 FTEs in the Moderate bracket, 6.1 FTEs in the High bracket, and 8.3 FTEs in the Very High bracket. +
A line graph shows that, as the maturity bracket increases, the average total FTE increases: The line graph data shows: 0.2 FTEs in the Very Low bracket, 2.5 FTEs in the Low bracket, 5.3 FTEs in the Moderate bracket, 6.1 FTEs in the High bracket, and 8.3 FTEs in the Very High bracket.
Figure 11. Average total Section 508 FTEs by maturity bracket
-
A line graph shows that, as the conformance bracket increases, the average total FTE generally increases:. The line graph data shows: 1.9 FTEs in the Very Low bracket, 6.1 FTEs in the Low bracket, 3.6 FTEs in the Moderate bracket, 4.9 FTEs in the High bracket, and 8.2 FTEs in the Very High bracket. +
A line graph shows that, as the conformance bracket increases, the average total FTE generally increases:. The line graph data shows: 1.9 FTEs in the Very Low bracket, 6.1 FTEs in the Low bracket, 3.6 FTEs in the Moderate bracket, 4.9 FTEs in the High bracket, and 8.2 FTEs in the Very High bracket.
Figure 12. Average total Section 508 FTEs by conformance bracket
@@ -114,7 +114,7 @@ Table 4 depicts the average hours per week Section 508 PMs dedicate to their Sec * 158 reporting entities (64%) said they had no or only some development and testing professionals trained in Section 508 web testing.
-
A bar graph shows the count of responses for inclusion of Section 508 conformance in ICT-related leadership/management performance plans (Q39): 68 respondents selected No, and have no plans to do so; 33 selected No, but reporting entity has a timetable to begin implementation; 42 selected Yes, for some ICT leadership and management performance plans; 7 selected Yes, for a majority of ICT leadership and management performance plans; 16 selected Yes, for all or almost all ICT leadership and management performance plans; and 83 selected Unknown. +
A bar graph shows the count of responses for inclusion of Section 508 conformance in ICT-related leadership/management performance plans (Q39): 68 respondents selected No, and have no plans to do so; 33 selected No, but reporting entity has a timetable to begin implementation; 42 selected Yes, for some ICT leadership and management performance plans; 7 selected Yes, for a majority of ICT leadership and management performance plans; 16 selected Yes, for all or almost all ICT leadership and management performance plans; and 83 selected Unknown.
Figure 13. Response count for inclusion of Section 508 conformance in ICT-related leadership and management performance plans (Q39)
@@ -187,7 +187,7 @@ Additional Training dimension highlights include: Across government, the state of Section 508 Programs also varied. Similar to reporting entity staffing, almost half of respondents (119 reporting entities or 48%) said they have no formal Section 508 Program or equivalent, or their formal Section 508 Program or equivalent is in development (as shown in the bottom two bars in Figure 14).
-
A bar graph shows the count of responses for status of Section 508 program or equivalent (Q22): 60 respondents selected 'does not have a formal Section 508 program or equivalent'; 59 selected 'formal Section 508 program or equivalent is in development and has the ability to provide support on an ad hoc basis'; 46 selected 'a Section 508 program or equivalent exists with defined organizational ownership'; 67 selected 'the Section 508 program or equivalent is widely known and relied on to inform policies, practices and decision-making related to digital content, technology development, and acquisitions'; and 17 selected 'the Section 508 program or equivalent has actively measured and well-defined performance metrics as well as authority in decision-making processes related to ICT'. +
A bar graph shows the count of responses for status of Section 508 program or equivalent (Q22): 60 respondents selected 'does not have a formal Section 508 program or equivalent'; 59 selected 'formal Section 508 program or equivalent is in development and has the ability to provide support on an ad hoc basis'; 46 selected 'a Section 508 program or equivalent exists with defined organizational ownership'; 67 selected 'the Section 508 program or equivalent is widely known and relied on to inform policies, practices and decision-making related to digital content, technology development, and acquisitions'; and 17 selected 'the Section 508 program or equivalent has actively measured and well-defined performance metrics as well as authority in decision-making processes related to ICT'.
Figure 14. Response count for status of Section 508 Program or equivalent (Q22)
@@ -204,7 +204,7 @@ Almost half of respondents (114 reporting entities or 46%) reported that * 14 reporting entities (6%) who did not know the status of their Section 508 policy.
-
A bar graph shows the count of responses for status of reporting entity Section 508 accessibility policy (Q27): 39 respondents selected that Section 508/ICT accessibility policy does not exist; 30 selected that Section 508/ICT accessibility policy in draft; 31 selected that High-level Section 508/ICT accessibility policy signed, but needs to be revised and/or more detail included; 73 selected that Signed, published Section 508/ICT accessibility policy that describes roles and responsibilities agency-wide for implementing and ensuring Section 508 requirements; 62 selected that Signed, published Section 508/ICT accessibility policy is appropriately referenced in other relevant agency policies and is regularly reviewed and updated; and 14 selected Unknown status of Section 508/ICT accessibility policy. +
A bar graph shows the count of responses for status of reporting entity Section 508 accessibility policy (Q27): 39 respondents selected that Section 508/ICT accessibility policy does not exist; 30 selected that Section 508/ICT accessibility policy in draft; 31 selected that High-level Section 508/ICT accessibility policy signed, but needs to be revised and/or more detail included; 73 selected that Signed, published Section 508/ICT accessibility policy that describes roles and responsibilities agency-wide for implementing and ensuring Section 508 requirements; 62 selected that Signed, published Section 508/ICT accessibility policy is appropriately referenced in other relevant agency policies and is regularly reviewed and updated; and 14 selected Unknown status of Section 508/ICT accessibility policy.
Figure 15. Response count for status of Section 508/ICT accessibility policy (Q27)
diff --git a/_pages/manage/annual-assessment/2023-report/2023-findings-testing-lifecycle.md b/_pages/manage/annual-assessment/2023-report/2023-findings-testing-lifecycle.md index a662864e0..dc81ac535 100644 --- a/_pages/manage/annual-assessment/2023-report/2023-findings-testing-lifecycle.md +++ b/_pages/manage/annual-assessment/2023-report/2023-findings-testing-lifecycle.md @@ -60,7 +60,7 @@ Similarly, the majority of respondents (153 reporting entities or 61%) r
-
Average percentage of respondents with automated testing tools by maturity category: Very Low: 30%, Low: 70%, Moderate: 68%, High: 92%, and Very High: 67%. +
Average percentage of respondents with automated testing tools by maturity category: Very Low: 30%, Low: 70%, Moderate: 68%, High: 92%, and Very High: 67%.
Figure 16. Average percentages of reporting entities with an automated testing tool by maturity brackets
@@ -68,7 +68,7 @@ Similarly, the majority of respondents (153 reporting entities or 61%) r
-
Average percentage of respondents with automated testing tools by performance category: Very Low: 43%, Low: 65%, Moderate: 89%, High: 72%, and Very High: 81%. +
Average percentage of respondents with automated testing tools by performance category: Very Low: 43%, Low: 65%, Moderate: 89%, High: 72%, and Very High: 81%.
Figure 17. Average percentages of reporting entities with an automated testing tool by conformance brackets
@@ -97,7 +97,7 @@ Similarly, the majority of respondents (153 reporting entities or 61%) r Additionally, when asked how often reporting entities conduct web content user testing with people with disabilities prior to deployment to address all applicable Section 508 standards, reporting entities overwhelmingly (217 respondents or 87%) reported they never or only sometimes conduct user testing with people with disabilities (see Figure 18 below.)
-
A bar graph shows the percentage of responses for how often reporting entities conducted web content user testing with PWD prior to deployment (Q7). Forty two percent (42%) of respondents selected 'never conducts user testing with PWD on web content for Section 508 conformance'; 45% selected 'sometimes conducts user testing with PWD on web content for Section 508 conformance, but generally on an ad hoc basis'; 6% selected 'regularly conducts user testing with PWD on web content for Section 508 conformance'; 4% selected 'frequently conducts user testing with PWD on web content for Section 508 conformance prior to deployment'; 2% selected 'comprehensive user testing with PWD is integrated into development and deployment, resulting in almost no accessibility issues deployed to production environments'; and 1% selected 'N/A - does not publish or maintain any web content'. +
A bar graph shows the percentage of responses for how often reporting entities conducted web content user testing with PWD prior to deployment (Q7). Forty two percent (42%) of respondents selected 'never conducts user testing with PWD on web content for Section 508 conformance'; 45% selected 'sometimes conducts user testing with PWD on web content for Section 508 conformance, but generally on an ad hoc basis'; 6% selected 'regularly conducts user testing with PWD on web content for Section 508 conformance'; 4% selected 'frequently conducts user testing with PWD on web content for Section 508 conformance prior to deployment'; 2% selected 'comprehensive user testing with PWD is integrated into development and deployment, resulting in almost no accessibility issues deployed to production environments'; and 1% selected 'N/A - does not publish or maintain any web content'.
Figure 18. Percentage of responses for how often reporting entities conduct web content user testing with PWD prior to deployment (Q7)
@@ -112,7 +112,7 @@ Some reporting entities integrate accessibility throughout the technology lifecy * Half of all reporting entities reported they have a formal policy requiring inclusion of Section 508 requirements, and regularly, frequently, or almost always include Section 508 requirements in ICT governance processes. 20
-
A bar graph shows responses indicating the extent to which ICT accessibility is integrated throughout technology development lifecycle activities (Q45): 13 respondents selected that ICT accessibility considerations are never included; 76 selected that ICT accessibility considerations are sometimes included; 66 selected that ICT accessibility requirements are regularly included; 29 selected that ICT accessibility requirements are frequently and usability, accessibility and AT testing are performed, and post-implementation IT reviews are conducted; 30 selected that ICT accessibility requirements are almost always included and universal design best practices are followed and accessible component re-use and sharing of accessible concepts and solutions; and 35 selected N/A - does not have a formal technology development lifecycle. +
A bar graph shows responses indicating the extent to which ICT accessibility is integrated throughout technology development lifecycle activities (Q45): 13 respondents selected that ICT accessibility considerations are never included; 76 selected that ICT accessibility considerations are sometimes included; 66 selected that ICT accessibility requirements are regularly included; 29 selected that ICT accessibility requirements are frequently and usability, accessibility and AT testing are performed, and post-implementation IT reviews are conducted; 30 selected that ICT accessibility requirements are almost always included and universal design best practices are followed and accessible component re-use and sharing of accessible concepts and solutions; and 35 selected N/A - does not have a formal technology development lifecycle.
Figure 19. Response count indicating the extent to which ICT accessibility is integrated throughout technology development lifecycle activities (Q45)
@@ -165,7 +165,7 @@ As demonstrated by low conformance, governmentwide, non-conformant ICT is preval * Specifically related to web remediation, 120 reporting entities (48%) said they never remediate Section 508 conformance issues after deployment, or they only sometimes do so mostly on an ad hoc basis.
-
A donut chart shows the percentages of responses for how non-conformant digital content is tracked and remediated (<a href='{{site.baseurl}}/manage/section-508-assessment/criteria-05/#q36'>Q36</a>): 25% of respondents selected that reporting entity does not track non-conformant digital content; 27% selected that reporting entity tracks but only sometimes takes action to remediate the content; 19% selected that reporting entity tracks and regularly creates and takes action on a plan to remediate; 17% selected that reporting entity tracks and frequently creates and takes action on a plan to remediate; and 13% selected that reporting entity always or almost always creates conformant content that does not require remediation/agency always or almost always takes action on a plan to remediate. +
A donut chart shows the percentages of responses for how non-conformant digital content is tracked and remediated (<a href='{{site.baseurl}}/manage/section-508-assessment/criteria-05/#q36'>Q36</a>): 25% of respondents selected that reporting entity does not track non-conformant digital content; 27% selected that reporting entity tracks but only sometimes takes action to remediate the content; 19% selected that reporting entity tracks and regularly creates and takes action on a plan to remediate; 17% selected that reporting entity tracks and frequently creates and takes action on a plan to remediate; and 13% selected that reporting entity always or almost always creates conformant content that does not require remediation/agency always or almost always takes action on a plan to remediate.
Figure 20. Percentages of responses for how non-conformant digital content is tracked and remediated (Q36)
diff --git a/_pages/manage/annual-assessment/2024-report/2024-appx-a-terms.md b/_pages/manage/annual-assessment/2024-report/2024-appx-a-terms.md index 83759a748..3be094a5e 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-appx-a-terms.md +++ b/_pages/manage/annual-assessment/2024-report/2024-appx-a-terms.md @@ -59,11 +59,11 @@ The following terms are used in this 2023 Assessment report to Congress. Additio Business Function Maturity - Or simply “maturity,” as it is referenced throughout this document, approximates the level of development and advancement of a reporting entity’s Section 508 Program as well as other functions across the organization, or business, that are relevant to digital accessibility. It assesses the reporting entity’s responses to the criteria within 9 maturity dimensions (Q29-Q66 See FY24 Data Dictionary (XLSX))). These questions cover different aspects of their Section 508 Program or equivalent as well as accessibility-related activities across the organization. Business function maturity, or “maturity,” is evaluated by the maturity index or “m-index” and utilizes a scale ranging from 0 to 5, with 0 indicating a very low maturity level and 5 indicating a very high maturity level. + Or simply “maturity,” as it is referenced throughout this document, approximates the level of development and advancement of a reporting entity’s Section 508 Program as well as other functions across the organization, or business, that are relevant to digital accessibility. It assesses the reporting entity’s responses to the criteria within 9 maturity dimensions (Q29-Q66 See FY24 Data Dictionary (XLSX))). These questions cover different aspects of their Section 508 Program or equivalent as well as accessibility-related activities across the organization. Business function maturity, or “maturity,” is evaluated by the maturity index or “m-index” and utilizes a scale ranging from 0 to 5, with 0 indicating a very low maturity level and 5 indicating a very high maturity level. C-Index - Assesses reporting entity conformance related to approximation of conformance to Section 508 standards. It measures how well reporting entities meet specific criteria within the Conformance dimension, using numerical values and weights for 16 criteria, including Q69a, Q71, Q74a, Q76, Q77, Q78, and Q80 to Q89. (See FY24 Data Dictionary (XLSX).) The index uses a scale from 0 to 5, with 0 representing very low and 5 representing very high conformance levels. + Assesses reporting entity conformance related to approximation of conformance to Section 508 standards. It measures how well reporting entities meet specific criteria within the Conformance dimension, using numerical values and weights for 16 criteria, including Q69a, Q71, Q74a, Q76, Q77, Q78, and Q80 to Q89. (See FY24 Data Dictionary (XLSX).) The index uses a scale from 0 to 5, with 0 representing very low and 5 representing very high conformance levels. Category @@ -110,7 +110,7 @@ The following terms are used in this 2023 Assessment report to Congress. Additio Criteria - Refers to the 103 Assessment criteria (See FY24 Data Dictionary (XLSX)) that reporting entities responded to, split into 11 dimensions. Due to dependencies, some reporting entities may have responded to fewer than 103 criteria. Also denoted with “Q” before a number to identify specific criteria referenced. The terms criteria, metric, and question are used interchangeably when referring to the content to which reporting entities responded. + Refers to the 103 Assessment criteria (See FY24 Data Dictionary (XLSX)) that reporting entities responded to, split into 11 dimensions. Due to dependencies, some reporting entities may have responded to fewer than 103 criteria. Also denoted with “Q” before a number to identify specific criteria referenced. The terms criteria, metric, and question are used interchangeably when referring to the content to which reporting entities responded. Dimension @@ -170,7 +170,7 @@ The following terms are used in this 2023 Assessment report to Congress. Additio Operational Conformance - Or simply referenced as “Conformance” throughout this document. Operational conformance approximates how effectively reporting entities adhere to the relevant requirements for Section 508. Operational conformance is measured by the conformance index or “c-index,” which assesses a reporting entity conformance by quantifying their responses to 16 specific criteria within the Conformance dimension. These criteria include Q69a, Q71, Q74a, Q76, Q77, Q78, and Q80-Q89 (See FY24 Data Dictionary (XLSX)). Each of these criteria is assigned numerical values and weights to determine overall conformance. + Or simply referenced as “Conformance” throughout this document. Operational conformance approximates how effectively reporting entities adhere to the relevant requirements for Section 508. Operational conformance is measured by the conformance index or “c-index,” which assesses a reporting entity conformance by quantifying their responses to 16 specific criteria within the Conformance dimension. These criteria include Q69a, Q71, Q74a, Q76, Q77, Q78, and Q80-Q89 (See FY24 Data Dictionary (XLSX)). Each of these criteria is assigned numerical values and weights to determine overall conformance. diff --git a/_pages/manage/annual-assessment/2024-report/2024-appx-b-methods.md b/_pages/manage/annual-assessment/2024-report/2024-appx-b-methods.md index c96770e56..abc0166f2 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-appx-b-methods.md +++ b/_pages/manage/annual-assessment/2024-report/2024-appx-b-methods.md @@ -91,7 +91,7 @@ GSA and OMB received data submissions from 245 reporting entities between May 29 ## Data Validation -GSA developed a script to systematically validate data submitted by reporting entities. Like FY23, this script primarily operated according to conditional if-then logic, relying on interconnections between different response options for a given reporting entity. When the validation tests identified inconsistencies among the response options for a given reporting entity, they triggered flags. While GSA categorized and tabulated these flags, it did not alter or remove any data for analysis. Please refer to the "Data Validation for FY24 Governmentwide Annual Assessment" for a summary of validation tests, associated flag counts, and the validation script written in R. +GSA developed a script to systematically validate data submitted by reporting entities. Like FY23, this script primarily operated according to conditional if-then logic, relying on interconnections between different response options for a given reporting entity. When the validation tests identified inconsistencies among the response options for a given reporting entity, they triggered flags. While GSA categorized and tabulated these flags, it did not alter or remove any data for analysis. Please refer to the "Data Validation for FY24 Governmentwide Annual Assessment" for a summary of validation tests, associated flag counts, and the validation script written in R. ## Descriptive Analysis @@ -333,7 +333,7 @@ Throughout this report, we present mean values or averages to provide a straight ## Regression Analysis -Regression analysis helps explore the relationships between independent variables and Section 508 compliance outcomes. For FY24, we conducted 22 regressions (XLSX) using both simple and multivariable models to explore which criteria, and to what extent, drive Section 508 program maturity and conformance. However, none of these regressions resulted in both a p-value below the threshold for statistical significance (0.05) and a high R² value (above 0.75). This suggests that while the models captured relevant factors, other dynamics such as data quality issues persist or may have compounded, hindering efforts to isolate the specific drivers of Section 508 compliance. +Regression analysis helps explore the relationships between independent variables and Section 508 compliance outcomes. For FY24, we conducted 22 regressions (XLSX) using both simple and multivariable models to explore which criteria, and to what extent, drive Section 508 program maturity and conformance. However, none of these regressions resulted in both a p-value below the threshold for statistical significance (0.05) and a high R² value (above 0.75). This suggests that while the models captured relevant factors, other dynamics such as data quality issues persist or may have compounded, hindering efforts to isolate the specific drivers of Section 508 compliance. Given the lack of statistically significant findings and the absence of high R² values, detailed regression methods and results are not included in this year's report. However, a condensed methodology is provided below and [full regression methods]({{site.baseurl}}/manage/section-508-assessment/2023/appendix-c-methods/) and [earlier findings]({{site.baseurl}}/manage/section-508-assessment/2023/assessment-data-downloads/) remain available for reference in the previous year's report. diff --git a/_pages/manage/annual-assessment/2024-report/2024-appx-c-entity-summary-report.html b/_pages/manage/annual-assessment/2024-report/2024-appx-c-entity-summary-report.html index 972d43c05..6b0710b61 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-appx-c-entity-summary-report.html +++ b/_pages/manage/annual-assessment/2024-report/2024-appx-c-entity-summary-report.html @@ -409,7 +409,7 @@

FY24 Governmentwide Section 508 Assessment (PDF) -* Regression Results for FY24 Governmentwide Section 508 Assessment (XLSX) -* Reporting Entity Response Data for FY24 Governmentwide Section 508 Assessment (CSV) -* Reporting Entity Response Data for FY24 Governmentwide Section 508 Assessment (JSON) -* Pre and Post Analysis For FY24 Governmentwide Section 508 Assessment (XLSX) -* Data Dictionary for FY24 Governmentwide Section 508 Assessment Final (XLSX) -* Data Validation for FY24 Governmentwide Annual Assessment (DOCX) +* FY24 Governmentwide Section 508 Assessment (PDF) +* Regression Results for FY24 Governmentwide Section 508 Assessment (XLSX) +* Reporting Entity Response Data for FY24 Governmentwide Section 508 Assessment (CSV) +* Reporting Entity Response Data for FY24 Governmentwide Section 508 Assessment (JSON) +* Pre and Post Analysis For FY24 Governmentwide Section 508 Assessment (XLSX) +* Data Dictionary for FY24 Governmentwide Section 508 Assessment Final (XLSX) +* Data Validation for FY24 Governmentwide Annual Assessment (DOCX) **Reviewed/Updated**: January 2025 \ No newline at end of file diff --git a/_pages/manage/annual-assessment/2024-report/2024-findings-acquisition.md b/_pages/manage/annual-assessment/2024-report/2024-findings-acquisition.md index 547bf69c6..b04933662 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-findings-acquisition.md +++ b/_pages/manage/annual-assessment/2024-report/2024-findings-acquisition.md @@ -22,7 +22,7 @@ Of the 239 entities who release solicitations, 171 entities or 71.5% reported IC Similar to last year, we still see a varied approach to verifying contract deliverables that are required to be Section 508 conformant. There was a reported increase this year in the number of entities who almost always verify digital accessibility requirements prior to acceptance, with 58 entities or 23.7% compared to 39 entities or 16% in FY23 selecting this response. However, 109 entities, or 46.6%, sometimes or never verify the accessibility of contract deliverables. **While this is a slight decrease compared to FY23** when 53% of entities reported an inconsistent verification approach, **this is still a very high percentage of entities who are accepting contract deliverables without knowing if they meet the contractual requirements for digital accessibility**. Figure 19 depicts the full breakdown of responses and comparison with FY23.
-
Bar chart showing YOY comparison of response count of approaches to verifying contract deliverables that are required to be Section 508 conformant (Q60), showing: 23 entities never verify down from 28 in FY23, 86 entities sometimes verify, down from 99 in FY23, 33 entities regularly verify down from 54 in FY23, 34 entities frequently verify up from 21 in FY23, 58 entities almost always verify up from 39 in FY23, and 11 did not know in FY24 compared to 8 in FY23. +
Bar chart showing YOY comparison of response count of approaches to verifying contract deliverables that are required to be Section 508 conformant (Q60), showing: 23 entities never verify down from 28 in FY23, 86 entities sometimes verify, down from 99 in FY23, 33 entities regularly verify down from 54 in FY23, 34 entities frequently verify up from 21 in FY23, 58 entities almost always verify up from 39 in FY23, and 11 did not know in FY24 compared to 8 in FY23.
Figure 19: YOY comparison of response count of approaches to verifying contract deliverables (Q60).
@@ -55,7 +55,7 @@ The Assessment asked a new question this year to better understand how reporting Following a FY23 Assessment recommendation for entities to increase inclusion of users with disabilities throughout the technology lifecycle, criteria continued to survey how the needs of individuals with disabilities are included during assessment of ICT-related business needs or equivalent acquisition planning process. The responses indicate a moderate, meaningful YOY increase (WRST: extremely statistically significant) and showed improvement with 75% fewer entities reporting that needs are not considered and almost 22% fewer entities noted that needs are sometimes considered but generally on an ad hoc basis. In addition, **56% more entities noted that needs are frequently considered and 72% more entities reported that needs are integrated into the business process and are almost always included**.
-
Bar chart showing YOY comparison of percentage of responses for inclusion of people with disabilities during the assessment of ICT-related business needs or equivalent acquisition planning process (Q61) showing that 29 entities in FY24 did not known, 8 entities do not include down from 32 in FY23, 76 entities sometimes include down from 110 in FY23, 42 entities regularly include for both years, 39 entities frequently include up from 25 in FY23, 43 entities almost always include up from 25 in FY23, and 8 selected N/A in FY24 compared to 15 in FY23. +
Bar chart showing YOY comparison of percentage of responses for inclusion of people with disabilities during the assessment of ICT-related business needs or equivalent acquisition planning process (Q61) showing that 29 entities in FY24 did not known, 8 entities do not include down from 32 in FY23, 76 entities sometimes include down from 110 in FY23, 42 entities regularly include for both years, 39 entities frequently include up from 25 in FY23, 43 entities almost always include up from 25 in FY23, and 8 selected N/A in FY24 compared to 15 in FY23.
Figure 20. YOY comparison of percentage of responses for inclusion of PWD during the assessment of ICT-related business needs or equivalent acquisition planning process (Q61).
@@ -169,7 +169,7 @@ Further analysis on the three types of exceptions covered in the Assessment show * Of entities who used this exception, the average was 8 fundamental alteration exceptions approved in FY24.
-
A bar chart showing the total number of authorized Fundamental Alteration Exceptions in FY23 was 2734 compared to 122 in FY24. +
A bar chart showing the total number of authorized Fundamental Alteration Exceptions in FY23 was 2734 compared to 122 in FY24.
Figure 21: Comparison of total approved Fundamental Alteration Exceptions.
@@ -186,7 +186,7 @@ Further analysis on the three types of exceptions covered in the Assessment show * Of entities who used this exception, the average was 1.6 Undue Burden exceptions approved in FY24.
-
A bar chart showing the total number of authorized Undue Burden Exceptions in FY23 was 20 compared to 8 in FY24. +
A bar chart showing the total number of authorized Undue Burden Exceptions in FY23 was 20 compared to 8 in FY24.
Figure 22: Comparison of total approved Undue Burden Exceptions.
@@ -203,7 +203,7 @@ Further analysis on the three types of exceptions covered in the Assessment show * Of the entities who used this exception, the average was 57 Best Meets exceptions approved in FY24.
-
A bar chart showing the total number of authorized Best Meets Exceptions in FY23 was 2774 compared to 1944 in FY24. +
A bar chart showing the total number of authorized Best Meets Exceptions in FY23 was 2774 compared to 1944 in FY24.
Figure 23: Comparison of total approved Best Meets Exceptions . diff --git a/_pages/manage/annual-assessment/2024-report/2024-findings-complaints.md b/_pages/manage/annual-assessment/2024-report/2024-findings-complaints.md index 9193180bc..1717d379e 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-findings-complaints.md +++ b/_pages/manage/annual-assessment/2024-report/2024-findings-complaints.md @@ -38,7 +38,7 @@ As shown in Figure 24, entities were asked to indicate to what extent the report * 17 entities (7%) selected unknown.
-
Bar chart showing FY24 response count for formal, written policies and procedures for processing and resolving complaints filed in relation to Section 508 nonconformance issues (Q36) shows 30 entities have no documented process, 80 entities have an ad hoc process, 35 entities have a documented process without tracking system, 49 entities have a documented process with a tracking system, 34 entities have a documented process with tracking and feedback systems, and 17 selected unknown. +
Bar chart showing FY24 response count for formal, written policies and procedures for processing and resolving complaints filed in relation to Section 508 nonconformance issues (Q36) shows 30 entities have no documented process, 80 entities have an ad hoc process, 35 entities have a documented process without tracking system, 49 entities have a documented process with a tracking system, 34 entities have a documented process with tracking and feedback systems, and 17 selected unknown.
Figure 24. FY24 response count of formal, written policies and procedures for processing and resolving complaints filed in relation to Section 508 nonconformance issues (Q36).
diff --git a/_pages/manage/annual-assessment/2024-report/2024-findings-key-compliance.md b/_pages/manage/annual-assessment/2024-report/2024-findings-key-compliance.md index 33e068458..98e76c414 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-findings-key-compliance.md +++ b/_pages/manage/annual-assessment/2024-report/2024-findings-key-compliance.md @@ -128,7 +128,7 @@ Entities reported predominantly using hybrid or manual test processes for **inte The Assessment continued to ask entities to test their top 10 viewed internet web pages, intranet web pages, and electronic documents and top five viewed videos. As Figure 3 shows, **on average, about half of respondents reported they did not have resources to test any of their top viewed ICT, which remains a high number**. With the exception of intranet web pages, slightly more entities submitted results this year for top viewed pieces of ICT and the percentage of conformance of the top viewed ICT slightly improved. **However, it is apparent in submitted data that entities do not have, or are not prioritizing, available resources to test ICT they procure, develop, maintain or use**.
-
Stacked bar charts comparing responses for top-viewed ICT YOY.  Top internet pages shows: 48% submitted results in FY23 increasing to 50% in FY24, 51% had no resources to test in FY23 declining to 47% in FY24, and 1% did not have internet pages in FY23 increasing to 3% in FY24. Top intranet pages shows: 37% submitted results in FY23 increasing to 32% in FY24, 55% had no resources to test in FY23 increasing to 58% in FY24 and 9% had no intranet pages in FY23 increasing to 10% in FY24. Top electronic documents show: 41% submitted results in FY23 increasing to 42% in FY24, 57% had no resources to test in FY23 decreasing to 53% in FY24 and 2% had no documents in FY23 increasing to 4% in FY24. Top videos show: 35% submitted results in FY23 increasing to 38% in FY24, 55% had no resources to test in FY23 decreasing to 47% in FY24 and 10% did not produce videos in FY23 increasing to 16% in FY24. +
Stacked bar charts comparing responses for top-viewed ICT YOY.  Top internet pages shows: 48% submitted results in FY23 increasing to 50% in FY24, 51% had no resources to test in FY23 declining to 47% in FY24, and 1% did not have internet pages in FY23 increasing to 3% in FY24. Top intranet pages shows: 37% submitted results in FY23 increasing to 32% in FY24, 55% had no resources to test in FY23 increasing to 58% in FY24 and 9% had no intranet pages in FY23 increasing to 10% in FY24. Top electronic documents show: 41% submitted results in FY23 increasing to 42% in FY24, 57% had no resources to test in FY23 decreasing to 53% in FY24 and 2% had no documents in FY23 increasing to 4% in FY24. Top videos show: 35% submitted results in FY23 increasing to 38% in FY24, 55% had no resources to test in FY23 decreasing to 47% in FY24 and 10% did not produce videos in FY23 increasing to 16% in FY24.
Figure 3. YOY Comparison of percentages of respondents submitting conformance testing results for the top intranet and internet web pages, electronic documents, and videos (Q71, Q76-78).
@@ -193,7 +193,7 @@ The **governmentwide Section 508 compliance for the top viewed ICT remains Low, * 34% of the top five viewed videos fully conforming to Section 508 standards.
-
Comparison bar charts showing top viewed ICT that fully conforms: 22% of top viewed internet pages fully conformed in FY23 compared to 23% in FY24; 25% of top viewed intranet pages fully conformed in FY23 compared to 20% in FY24; 24% of top viewed documents fully conformed in FY23 compared to 25% in FY24; and 29% of top viewed videos fully conformed in FY23 compared to 34% in FY24. +
Comparison bar charts showing top viewed ICT that fully conforms: 22% of top viewed internet pages fully conformed in FY23 compared to 23% in FY24; 25% of top viewed intranet pages fully conformed in FY23 compared to 20% in FY24; 24% of top viewed documents fully conformed in FY23 compared to 25% in FY24; and 29% of top viewed videos fully conformed in FY23 compared to 34% in FY24.
Figure 4. YOY comparison of percentage of fully conformant ICT for all top intranet web pages, internet web pages, electronic documents, and videos tested (Q71 to Q76-78)
@@ -433,7 +433,7 @@ While 100% conformance is the Section 508 standard, few entities reported full c
-
Bar chart showing percentage of entities reporting full conformance by ICT products. Results show: 12.2% for reservation system, 15.1% for survey tools, 11.4% for surveys, 32.7% for messaging or chat system, 13.9% for LMS, 42.4% for Section 508 Policy, 22.9% for video player, 26.5% for public form, 19.6% for FY25 CJ, and 6.9% for performance portal. +
Bar chart showing percentage of entities reporting full conformance by ICT products. Results show: 12.2% for reservation system, 15.1% for survey tools, 11.4% for surveys, 32.7% for messaging or chat system, 13.9% for LMS, 42.4% for Section 508 Policy, 22.9% for video player, 26.5% for public form, 19.6% for FY25 CJ, and 6.9% for performance portal.
Figure 5. Percentages of entities reporting 100% conformance for commonly used ICT products.
@@ -442,7 +442,7 @@ While 100% conformance is the Section 508 standard, few entities reported full c The number of reporting entities with 90% or more conformance for ICT products increased , which suggests that while some ICT products may still have some accessibility issues, they may be close to fully conformant. The highest conformance percentage was still the publicly posted Section 508 policy at 61.2% of entities who conform to 90% or more of the standards followed closely again by enterprise-wide chat or real-time messaging system at 60.8% of entities. However, the lowest conforming category was surveys released by entities, with only 27.8% of reporting entities noting conformance with 90% or more of standards. 
-
Bar chart showing percentage of entities reporting 90% or more conformance by ICT products. Results show: 28.2% for reservation system, 31.4% for survey tools, 27.8% for surveys, 60.8% for messaging or chat system, 39.6% for LMS, 61.2% for Section 508 Policy, 42.9% for video player, 44.1% for public form, 32.2% for FY25 CJ, and 31.4% for performance portal. +
Bar chart showing percentage of entities reporting 90% or more conformance by ICT products. Results show: 28.2% for reservation system, 31.4% for survey tools, 27.8% for surveys, 60.8% for messaging or chat system, 39.6% for LMS, 61.2% for Section 508 Policy, 42.9% for video player, 44.1% for public form, 32.2% for FY25 CJ, and 31.4% for performance portal.
Figure 6. Percentage of reporting entities reporting 90% or more conformance by products used internally and by the public (Q80-Q89).
diff --git a/_pages/manage/annual-assessment/2024-report/2024-findings-key-maturity.md b/_pages/manage/annual-assessment/2024-report/2024-findings-key-maturity.md index 4a6f50200..4fa559a16 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-findings-key-maturity.md +++ b/_pages/manage/annual-assessment/2024-report/2024-findings-key-maturity.md @@ -21,7 +21,7 @@ This Assessment targets two key areas of analysis to determine performance with GSA combined the reporting entities' self-reported responses to get one estimate of a reporting entity's overall performance. Like last year, the maturity and conformance indices -- based solely on the assessment responses -- provide a comprehensive and quantitative assessment of Section 508 compliance across the federal government. The business function maturity index, referred to as "maturity" or "m-index," quantified reporting entity responses to criteria across nine dimensions with equal weighting of each criteria. The operational conformance matrix, referred to as "conformance" or "c-index," quantified 16 specific criteria in the Conformance dimension to assess how well reporting entities performed with respect to Section 508 implementation. The indices are on a 5-point scale, from zero to five. These indices are fully described in [Appendix B: Methods, Descriptive Analysis]({{site.baseurl}}/manage/section-508-assessment/2024/appendix-b-methods/). 
-
Scatter plot with trendline of all reporting entities' conformance and maturity index results. There is a concentration of reporting entities towards the center of the graph, with less towards the bottom left corner of the graph (the lower performers) and an even smaller number of reporting entities in the top right corner (the higher performers). The trendline shows a positive relationship between maturity and conformance. Please see Table 6 for a full description of where entities fell on the five by five scatter plot. +
Scatter plot with trendline of all reporting entities' conformance and maturity index results. There is a concentration of reporting entities towards the center of the graph, with less towards the bottom left corner of the graph (the lower performers) and an even smaller number of reporting entities in the top right corner (the higher performers). The trendline shows a positive relationship between maturity and conformance. Please see Table 6 for a full description of where entities fell on the five by five scatter plot.
Figure 7. Scatter plot with trendline of all reporting entities' conformance and maturity index results
@@ -257,7 +257,7 @@ The highest performing maturity outcome was Content Creation at 2.69, followed b Below, the FY 24 outcomes are depicted in the chart:
-
Comparison bar chart showing average dimension outcomes YOY. Please see Table 8 for a table view of this data. +
Comparison bar chart showing average dimension outcomes YOY. Please see Table 8 for a table view of this data.
Figure 8. Average FY24 Maturity Dimension Outcomes with FY23 for Comparison
diff --git a/_pages/manage/annual-assessment/2024-report/2024-findings-program-staff.md b/_pages/manage/annual-assessment/2024-report/2024-findings-program-staff.md index 1a238b971..ef65068f7 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-findings-program-staff.md +++ b/_pages/manage/annual-assessment/2024-report/2024-findings-program-staff.md @@ -48,7 +48,7 @@ As shown in Figure 10, 33% of reporting entities reported a full-time Section 50
-
Bar chart comparison of governmentwide Section 508 PM or equivalent utilization showing 33% of entities reported a Full-time Section 508 PM in FY24 up from 28% in FY23, 56% reported a part-time PM in FY24 up from 51% in FY23 and 11% reported no Section 508 PM compared to 21% in FY23. +
Bar chart comparison of governmentwide Section 508 PM or equivalent utilization showing 33% of entities reported a Full-time Section 508 PM in FY24 up from 28% in FY23, 56% reported a part-time PM in FY24 up from 51% in FY23 and 11% reported no Section 508 PM compared to 21% in FY23.
Figure 10. Comparison of governmentwide Section 508 PM or equivalent utilization (Q4)
@@ -116,7 +116,7 @@ While some entities reported increasing Section 508 staffing and contractor reso * Governmentwide, the FY24 average number of Section 508 FTEs was at 5.5 compared to 4.3 in FY23, comprising an average of 3.7 federal Section 508 FTEs versus 2.7 in FY23 and 1.8 contractor Section 508 FTEs versus 1.6 in FY23.24
-
Line graph showing average reporting entity FTEs by maturity bracket. For Very Low, the average number of FTEs was 0.7, Low’s average was 1.7 FTEs, Moderate’s average was 9 FTEs, High’s average was 5.7 FTEs and Very High’s average was 12.3 FTEs. There is a positive correlation between the total number of FTEs and the maturity outcomes. +
Line graph showing average reporting entity FTEs by maturity bracket. For Very Low, the average number of FTEs was 0.7, Low’s average was 1.7 FTEs, Moderate’s average was 9 FTEs, High’s average was 5.7 FTEs and Very High’s average was 12.3 FTEs. There is a positive correlation between the total number of FTEs and the maturity outcomes.
Figure 11. Average reporting entity FTE by maturity bracket.
@@ -125,7 +125,7 @@ While some entities reported increasing Section 508 staffing and contractor reso As Figure 11 shows, there is a positive correlation between the total number of FTEs and the maturity outcomes for that reporting entity. More well-resourced organizations tend to be more mature with respect to accessibility considerations across the business landscape. The reverse is also true: less mature organizations tend to be those that are not well resourced.
-
Line graph showing average reporting entity FTEs by conformance bracket. For Very Low, the average number of FTEs was 3.5, Low’s average was 6.4 FTEs, Moderate’s average was 5.8 FTEs, High’s average was 9.1 FTEs and Very High’s average was 3 FTEs. FTE by conformance shows a positive relationship between the number of resources and the conformance outcomes. +
Line graph showing average reporting entity FTEs by conformance bracket. For Very Low, the average number of FTEs was 3.5, Low’s average was 6.4 FTEs, Moderate’s average was 5.8 FTEs, High’s average was 9.1 FTEs and Very High’s average was 3 FTEs. FTE by conformance shows a positive relationship between the number of resources and the conformance outcomes.
Figure 12. Average reporting entity FTE by conformance bracket.
@@ -141,7 +141,7 @@ In the Assessment, FTE only factors in Section 508 FTEs directly supporting the Although the Human Capital, Culture, and Leadership Dimension improved from 1.63 in FY23 to 1.93 in FY24 – about an 18% increase YOY across the government – there is still room for improvement. This remains one of the lowest performing dimensions. In fact, in FY24, it is the lowest dimension. While improvements were reported, digital accessibility remains deprioritized for some reporting entities.
-
Line graph showing average reporting entity FTEs by conformance bracket. For Very Low, the average number of FTEs was 3.5, Low’s average was 6.4 FTEs, Moderate’s average was 5.8 FTEs, High’s average was 9.1 FTEs and Very High’s average was 3 FTEs. FTE by conformance shows a positive relationship between the number of resources and the conformance outcomes. +
Line graph showing average reporting entity FTEs by conformance bracket. For Very Low, the average number of FTEs was 3.5, Low’s average was 6.4 FTEs, Moderate’s average was 5.8 FTEs, High’s average was 9.1 FTEs and Very High’s average was 3 FTEs. FTE by conformance shows a positive relationship between the number of resources and the conformance outcomes.
Figure 13. YOY response count for inclusion of Section 508 conformance in ICT-related leadership and management performance plans (Q44).
diff --git a/_pages/manage/annual-assessment/2024-report/2024-findings-program.md b/_pages/manage/annual-assessment/2024-report/2024-findings-program.md index f7b767966..50c9790e4 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-findings-program.md +++ b/_pages/manage/annual-assessment/2024-report/2024-findings-program.md @@ -23,7 +23,7 @@ Please note the terms “reporting entity” and “respondent” are not synony The Assessment shows improvements in reporting entities’ Section 508 programs, specifically in the status, influence, and resourcing. Respondents reported a 135% increase in Section 508 programs that are widely known, relied upon, and have decision making authority. 40 entities selected this option in FY24 compared to only 17 in FY23. Furthermore, the YOY difference indicates an improvement in the available Section 508 resources such as training, tools, staff support, etc. In FY23, half of the reporting entities noted that while they did identify resource needs, the ones provided or available were insufficient to support the needs of the Section 508 program’s or equivalent. This improved in FY24 by a moderate, meaningful increase (WRST: extremely statistically significant), with half of the reporting entities (from 1% to 59%) indicating some resource needs are met. At the same time, we observed a 20% YOY improvement in the number of entities who stated they have no formal Section 508 program or that the program was in development, with 39% of entities selecting these options in FY24 compared to 48% in FY23.
-
Bar chart showing YOY comparison of response count for status of Section 508 program or equivalent (Q29). In FY24, 50 entities selected they have no formal program down from 60 in FY23, 45 entities in FY24 selected their program is in development down from 59 in FY23, 58 entities in FY24 selected their program is established with organizational ownership up from 46 in FY23, 51 entities in FY24 selected their program is established and relied upon for decision making, down from 67 in FY23, and 40 entities in FY24 noted their program is well-known with performance metrics and decision making authority, up from 17 in FY23. +
Bar chart showing YOY comparison of response count for status of Section 508 program or equivalent (Q29). In FY24, 50 entities selected they have no formal program down from 60 in FY23, 45 entities in FY24 selected their program is in development down from 59 in FY23, 58 entities in FY24 selected their program is established with organizational ownership up from 46 in FY23, 51 entities in FY24 selected their program is established and relied upon for decision making, down from 67 in FY23, and 40 entities in FY24 noted their program is well-known with performance metrics and decision making authority, up from 17 in FY23.
Figure 14. YOY comparison of response count for status of Section 508 program or equivalent (Q29).
@@ -42,7 +42,7 @@ The same number of entities (39) reported YOY that their Section 508 or ICT acce * 41 entities noting the Section 508 policy is published, includes all relevant M-24-08 and Section 508 statutory requirements, and is referenced in other relevant policies.
-
Bar chart of FY24 response count for status of Section 508 or ICT accessibility policy (Q34) showing 39 entities do not have a policy, 74 entities have a draft policy, 45 entities have a published policy without relevant statutory requirements, 39 entities have a published policy with relevant statutory requirements, 41 entities have a published policy with relevant statutory requirements and referenced in other policies, and 7 entities do not know the status of their policy. +
Bar chart of FY24 response count for status of Section 508 or ICT accessibility policy (Q34) showing 39 entities do not have a policy, 74 entities have a draft policy, 45 entities have a published policy without relevant statutory requirements, 39 entities have a published policy with relevant statutory requirements, 41 entities have a published policy with relevant statutory requirements and referenced in other policies, and 7 entities do not know the status of their policy.
Figure 15. FY24 response count for status of Section 508 or ICT accessibility policy (Q34).
diff --git a/_pages/manage/annual-assessment/2024-report/2024-findings-testing-lifecycle.md b/_pages/manage/annual-assessment/2024-report/2024-findings-testing-lifecycle.md index cfbcdde66..976a2d663 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-findings-testing-lifecycle.md +++ b/_pages/manage/annual-assessment/2024-report/2024-findings-testing-lifecycle.md @@ -120,7 +120,7 @@ Additionally, YOY data revealed no change, with 61% of reporting entities, or 15
-
Line graph showing percentage of entities with an automated testing tool by Maturity Bracket: Very Low: 28%, Low: 39%, Moderate: 71%, High: 80%, and Very High: 93%. Generally, the higher the maturity, the higher the percentage of reporting entities with automated testing tools. +
Line graph showing percentage of entities with an automated testing tool by Maturity Bracket: Very Low: 28%, Low: 39%, Moderate: 71%, High: 80%, and Very High: 93%. Generally, the higher the maturity, the higher the percentage of reporting entities with automated testing tools.
Figure 16. Percentage of entities with an automated testing tool by Maturity Bracket.
@@ -128,7 +128,7 @@ Additionally, YOY data revealed no change, with 61% of reporting entities, or 15
-
Line graph showing percentage of entities with an automated testing tool by conformance Bracket: Very Low: 42%, Low: 67%, Moderate: 64%, High: 82%, and Very High: 92%.Generally, the higher the conformance, the higher the percentage of reporting entities with automated testing tools. +
Line graph showing percentage of entities with an automated testing tool by conformance Bracket: Very Low: 42%, Low: 67%, Moderate: 64%, High: 82%, and Very High: 92%.Generally, the higher the conformance, the higher the percentage of reporting entities with automated testing tools.
Figure 17. Percentage of entities with an automated testing tool by Conformance Bracket.
@@ -180,7 +180,7 @@ The Assessment continued to ask how the reporting entity escalates and takes act Furthermore, the Assessment asked how entities remediate nonconformant ICT that is deployed or distributed, with **35% of entities sometimes or never taking action for remediation, down from 48% in FY23**. This difference indicates a moderate, meaningful increase (WRST: extremely statistically significant) to improve the remediation efforts of nonconformance issues. As Figure 18 shows, 20% almost always immediately remediate high-severity issues, an improvement from 10% in FY23, leading to an 88% increase. Reporting entities are making investments in their remediation efforts that may be more evident in conformance outcomes in future years.
-
Bar chart showing YOY response count comparison of how known nonconformance issues are remediated after deployment or distribution of ICT (Q56) showing 13 entities never remediate up from 6 in FY23, 81 entities sometimes remediate down from 107 in FY23, 33 entities regularly remediate down from 52 in FY23, 33 entities frequently remediate compared to 31 in FY23, 49 entities almost always remediate, up from 26 in FY23 and 23 entities responded Unknown in FY24 compared to 20 in FY23. +
Bar chart showing YOY response count comparison of how known nonconformance issues are remediated after deployment or distribution of ICT (Q56) showing 13 entities never remediate up from 6 in FY23, 81 entities sometimes remediate down from 107 in FY23, 33 entities regularly remediate down from 52 in FY23, 33 entities frequently remediate compared to 31 in FY23, 49 entities almost always remediate, up from 26 in FY23 and 23 entities responded Unknown in FY24 compared to 20 in FY23.
Figure 18. YOY response count comparison of how known nonconformance issues are remediated after deployment or distribution of ICT (Q56).
diff --git a/_pages/manage/annual-assessment/2024-report/2024-introduction.md b/_pages/manage/annual-assessment/2024-report/2024-introduction.md index 1b5ccf407..e17f49870 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-introduction.md +++ b/_pages/manage/annual-assessment/2024-report/2024-introduction.md @@ -52,7 +52,7 @@ The makeup of all [245 reporting entities]({{site.baseurl}}/manage/section-508-a OMB, in close coordination with GSA, the Access Board, the Office of Science and Technology Policy (OSTP), and the Department of Justice (DOJ), refined the assessment criteria from the previous year, incorporating feedback from agencies to thoroughly and efficiently evaluate reporting entity Section 508 compliance. For a complete list of changes, please reference the crosswalk between FY23 and FY24 criteria. GSA also refined additional context for understanding the criteria, Frequently Asked Questions (FAQs), and defining terms to help reporting entities collect accurate data for the Assessment. -OMB broadly distributed instructions and 103 assessment criteria to heads of agencies, agency Chief Information Officers (CIO), and Section 508 Program Managers (PM) on April 8, 2024. Additionally, GSA posted the instructions and criteria (XLSX) on Section508.gov the same day.  +OMB broadly distributed instructions and 103 assessment criteria to heads of agencies, agency Chief Information Officers (CIO), and Section 508 Program Managers (PM) on April 8, 2024. Additionally, GSA posted the instructions and criteria (XLSX) on Section508.gov the same day.  OMB deferred to departments and agencies to define how they would report: individually, by organizational unit or "reporting entity," or as a component of a larger parent agency. Reporting entities then designated a point of contact for the Assessment. GSA referenced and maintained, at the direction of OMB, a list of reporting entities and information for each point of contact. diff --git a/_pages/manage/annual-assessment/2024-report/2024-observations-acknowledgements.md b/_pages/manage/annual-assessment/2024-report/2024-observations-acknowledgements.md index 9db34092a..5ecb1dca2 100644 --- a/_pages/manage/annual-assessment/2024-report/2024-observations-acknowledgements.md +++ b/_pages/manage/annual-assessment/2024-report/2024-observations-acknowledgements.md @@ -41,7 +41,7 @@ Data validation findings continue to support the misinterpretation or misunderst * Validation 7.2 revealed in 48 failures where reporting entities indicated in Q55 that they use specific methods---options b), c), d), or e)---for testing electronic document conformance but did not select option d) in Q9, which indicates the use of a test process for electronic documents. To test electronic documents effectively, they also perform evaluations using a documented test process. The lack of alignment between Q55 and Q9 suggests a possible oversight or gap in the reporting entities' testing procedures. -Other data validation flags, such as contradictory responses or responses that exceed or do not total when required 100%, are denoted in Data Validation for FY24 Governmentwide Annual Assessment. +Other data validation flags, such as contradictory responses or responses that exceed or do not total when required 100%, are denoted in Data Validation for FY24 Governmentwide Annual Assessment. As with FY23, no data was excluded from analysis regardless of data validation outcomes for FY24. However, before conducting the 40 validation tests, GSA carried out a preliminary review to identify and address data discrepancies that would skew descriptive statistics related to conformance. This process included direct engagement with reporting entities to correct invalid data, which was undertaken in FY23. Specific discrepancies addressed during this preliminary review included: diff --git a/assets/css/index.scss b/assets/css/index.scss index e011ea26f..a87dfcd7c 100644 --- a/assets/css/index.scss +++ b/assets/css/index.scss @@ -1137,7 +1137,7 @@ div[role=rowheader] { #grid-index.vhvl { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) 0px -60px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) 0px -60px; display: block; margin-left: auto; margin-right: auto; @@ -1146,7 +1146,7 @@ div[role=rowheader] { #grid-index.vhl { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -255px -60px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -255px -60px; display: block; margin-left: auto; margin-right: auto; @@ -1155,7 +1155,7 @@ div[role=rowheader] { #grid-index.vhm { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -500px -60px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -500px -60px; display: block; margin-left: auto; margin-right: auto; @@ -1164,7 +1164,7 @@ div[role=rowheader] { #grid-index.vhh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -750px -60px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -750px -60px; display: block; margin-left: auto; margin-right: auto; @@ -1173,7 +1173,7 @@ div[role=rowheader] { #grid-index.vhvh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -1000px -60px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -1000px -60px; display: block; margin-left: auto; margin-right: auto; @@ -1183,7 +1183,7 @@ div[role=rowheader] { #grid-index.hvl { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) 0px -300px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) 0px -300px; display: block; margin-left: auto; margin-right: auto; @@ -1192,7 +1192,7 @@ div[role=rowheader] { #grid-index.hl { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -255px -300px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -255px -300px; display: block; margin-left: auto; margin-right: auto; @@ -1201,7 +1201,7 @@ div[role=rowheader] { #grid-index.hm { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -500px -300px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -500px -300px; display: block; margin-left: auto; margin-right: auto; @@ -1210,7 +1210,7 @@ div[role=rowheader] { #grid-index.hh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -750px -300px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -750px -300px; display: block; margin-left: auto; margin-right: auto; @@ -1219,7 +1219,7 @@ div[role=rowheader] { #grid-index.hvh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -1000px -300px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -1000px -300px; display: block; margin-left: auto; margin-right: auto; @@ -1229,7 +1229,7 @@ div[role=rowheader] { #grid-index.mvl { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) 0px -540px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) 0px -540px; display: block; margin-left: auto; margin-right: auto; @@ -1238,7 +1238,7 @@ div[role=rowheader] { #grid-index.ml { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -255px -540px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -255px -540px; display: block; margin-left: auto; margin-right: auto; @@ -1247,7 +1247,7 @@ div[role=rowheader] { #grid-index.mm { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -500px -540px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -500px -540px; display: block; margin-left: auto; margin-right: auto; @@ -1256,7 +1256,7 @@ div[role=rowheader] { #grid-index.mh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -750px -540px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -750px -540px; display: block; margin-left: auto; margin-right: auto; @@ -1265,7 +1265,7 @@ div[role=rowheader] { #grid-index.mvh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -1000px -540px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -1000px -540px; display: block; margin-left: auto; margin-right: auto; @@ -1275,7 +1275,7 @@ div[role=rowheader] { #grid-index.lvl { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) 0px -780px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) 0px -780px; display: block; margin-left: auto; margin-right: auto; @@ -1284,7 +1284,7 @@ div[role=rowheader] { #grid-index.ll { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -255px -780px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -255px -780px; display: block; margin-left: auto; margin-right: auto; @@ -1293,7 +1293,7 @@ div[role=rowheader] { #grid-index.lm { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -500px -780px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -500px -780px; display: block; margin-left: auto; margin-right: auto; @@ -1302,7 +1302,7 @@ div[role=rowheader] { #grid-index.lh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -750px -780px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -750px -780px; display: block; margin-left: auto; margin-right: auto; @@ -1311,7 +1311,7 @@ div[role=rowheader] { #grid-index.lvh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -1000px -780px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -1000px -780px; display: block; margin-left: auto; margin-right: auto; @@ -1321,7 +1321,7 @@ div[role=rowheader] { #grid-index.vlvl { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) 0px -1020px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) 0px -1020px; display: block; margin-left: auto; margin-right: auto; @@ -1330,7 +1330,7 @@ div[role=rowheader] { #grid-index.vll { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -255px -1020px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -255px -1020px; display: block; margin-left: auto; margin-right: auto; @@ -1339,7 +1339,7 @@ div[role=rowheader] { #grid-index.vlm { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -500px -1020px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -500px -1020px; display: block; margin-left: auto; margin-right: auto; @@ -1348,7 +1348,7 @@ div[role=rowheader] { #grid-index.vlh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -750px -1020px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -750px -1020px; display: block; margin-left: auto; margin-right: auto; @@ -1357,7 +1357,7 @@ div[role=rowheader] { #grid-index.vlvh { width: 160px; height: 160px; - background: url(https://assets.section508.gov/files/reports/cr-2023/g-index_sprite.png) -1000px -1020px; + background: url(https://assets.section508.gov/assets/images/assessment/fy23/g-index_sprite.png) -1000px -1020px; display: block; margin-left: auto; margin-right: auto; diff --git a/assets/images/bio-images-iaaf/bio-aiken.jpg b/assets/images/bio-images-iaaf/bio-aiken.jpg deleted file mode 100644 index 73c69a3ec..000000000 Binary files a/assets/images/bio-images-iaaf/bio-aiken.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-barrett.jpg b/assets/images/bio-images-iaaf/bio-barrett.jpg deleted file mode 100644 index af25eff06..000000000 Binary files a/assets/images/bio-images-iaaf/bio-barrett.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-blakely-hill.jpg b/assets/images/bio-images-iaaf/bio-blakely-hill.jpg deleted file mode 100644 index dd8c57256..000000000 Binary files a/assets/images/bio-images-iaaf/bio-blakely-hill.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-bonitto.jpg b/assets/images/bio-images-iaaf/bio-bonitto.jpg deleted file mode 100644 index 942d51047..000000000 Binary files a/assets/images/bio-images-iaaf/bio-bonitto.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-briscoe.jpg b/assets/images/bio-images-iaaf/bio-briscoe.jpg deleted file mode 100644 index 1551b83e5..000000000 Binary files a/assets/images/bio-images-iaaf/bio-briscoe.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-clark.jpg b/assets/images/bio-images-iaaf/bio-clark.jpg deleted file mode 100644 index 086ad4801..000000000 Binary files a/assets/images/bio-images-iaaf/bio-clark.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-cooper.jpg b/assets/images/bio-images-iaaf/bio-cooper.jpg deleted file mode 100644 index 0163197cc..000000000 Binary files a/assets/images/bio-images-iaaf/bio-cooper.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-creagan.png b/assets/images/bio-images-iaaf/bio-creagan.png deleted file mode 100644 index ad9eabc90..000000000 Binary files a/assets/images/bio-images-iaaf/bio-creagan.png and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-crowell.jpg b/assets/images/bio-images-iaaf/bio-crowell.jpg deleted file mode 100644 index a2514fd41..000000000 Binary files a/assets/images/bio-images-iaaf/bio-crowell.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-curtis-davidson.jpg b/assets/images/bio-images-iaaf/bio-curtis-davidson.jpg deleted file mode 100644 index 1397f702d..000000000 Binary files a/assets/images/bio-images-iaaf/bio-curtis-davidson.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-dhillon.jpg b/assets/images/bio-images-iaaf/bio-dhillon.jpg deleted file mode 100644 index e730b44f8..000000000 Binary files a/assets/images/bio-images-iaaf/bio-dhillon.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-eng.jpg b/assets/images/bio-images-iaaf/bio-eng.jpg deleted file mode 100644 index 976b9b889..000000000 Binary files a/assets/images/bio-images-iaaf/bio-eng.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-evans.jpg b/assets/images/bio-images-iaaf/bio-evans.jpg deleted file mode 100644 index 330b5dcb6..000000000 Binary files a/assets/images/bio-images-iaaf/bio-evans.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-farraj-feijoo.jpg b/assets/images/bio-images-iaaf/bio-farraj-feijoo.jpg deleted file mode 100644 index ebb41fc0c..000000000 Binary files a/assets/images/bio-images-iaaf/bio-farraj-feijoo.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-fern.jpg b/assets/images/bio-images-iaaf/bio-fern.jpg deleted file mode 100644 index 45d3b3a54..000000000 Binary files a/assets/images/bio-images-iaaf/bio-fern.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-francis.jpg b/assets/images/bio-images-iaaf/bio-francis.jpg deleted file mode 100644 index 99f1a1d41..000000000 Binary files a/assets/images/bio-images-iaaf/bio-francis.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-franks.jpg b/assets/images/bio-images-iaaf/bio-franks.jpg deleted file mode 100644 index 48aada34c..000000000 Binary files a/assets/images/bio-images-iaaf/bio-franks.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-fuoco.jpg b/assets/images/bio-images-iaaf/bio-fuoco.jpg deleted file mode 100644 index fa3d3cf89..000000000 Binary files a/assets/images/bio-images-iaaf/bio-fuoco.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-garrett.jpg b/assets/images/bio-images-iaaf/bio-garrett.jpg deleted file mode 100644 index 665c67494..000000000 Binary files a/assets/images/bio-images-iaaf/bio-garrett.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-gibson.jpg b/assets/images/bio-images-iaaf/bio-gibson.jpg deleted file mode 100644 index 8c613ad85..000000000 Binary files a/assets/images/bio-images-iaaf/bio-gibson.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-hailesselassie.jpg b/assets/images/bio-images-iaaf/bio-hailesselassie.jpg deleted file mode 100644 index 0899f5afb..000000000 Binary files a/assets/images/bio-images-iaaf/bio-hailesselassie.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-harkin.jpg b/assets/images/bio-images-iaaf/bio-harkin.jpg deleted file mode 100644 index b08766c55..000000000 Binary files a/assets/images/bio-images-iaaf/bio-harkin.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-hays.jpg b/assets/images/bio-images-iaaf/bio-hays.jpg deleted file mode 100644 index 4414a782f..000000000 Binary files a/assets/images/bio-images-iaaf/bio-hays.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-horton.jpg b/assets/images/bio-images-iaaf/bio-horton.jpg deleted file mode 100644 index 46ecf4a23..000000000 Binary files a/assets/images/bio-images-iaaf/bio-horton.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-humphrey.jpg b/assets/images/bio-images-iaaf/bio-humphrey.jpg deleted file mode 100644 index 2954cab97..000000000 Binary files a/assets/images/bio-images-iaaf/bio-humphrey.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-jacobs.jpg b/assets/images/bio-images-iaaf/bio-jacobs.jpg deleted file mode 100644 index bed17e490..000000000 Binary files a/assets/images/bio-images-iaaf/bio-jacobs.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-kevin-smith.jpg b/assets/images/bio-images-iaaf/bio-kevin-smith.jpg deleted file mode 100644 index 670f0c5d4..000000000 Binary files a/assets/images/bio-images-iaaf/bio-kevin-smith.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-kline.jpg b/assets/images/bio-images-iaaf/bio-kline.jpg deleted file mode 100644 index c42345afd..000000000 Binary files a/assets/images/bio-images-iaaf/bio-kline.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-kuk.jpg b/assets/images/bio-images-iaaf/bio-kuk.jpg deleted file mode 100644 index e48dbda42..000000000 Binary files a/assets/images/bio-images-iaaf/bio-kuk.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-langevin.jpg b/assets/images/bio-images-iaaf/bio-langevin.jpg deleted file mode 100644 index 737302db6..000000000 Binary files a/assets/images/bio-images-iaaf/bio-langevin.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-laurin.jpg b/assets/images/bio-images-iaaf/bio-laurin.jpg deleted file mode 100644 index 49fb5ed51..000000000 Binary files a/assets/images/bio-images-iaaf/bio-laurin.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-leblois.jpg b/assets/images/bio-images-iaaf/bio-leblois.jpg deleted file mode 100644 index dba1577da..000000000 Binary files a/assets/images/bio-images-iaaf/bio-leblois.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-malakhoff.jpg b/assets/images/bio-images-iaaf/bio-malakhoff.jpg deleted file mode 100644 index 085de89f2..000000000 Binary files a/assets/images/bio-images-iaaf/bio-malakhoff.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-manuel.jpg b/assets/images/bio-images-iaaf/bio-manuel.jpg deleted file mode 100644 index 87ce986ed..000000000 Binary files a/assets/images/bio-images-iaaf/bio-manuel.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-moore.jpg b/assets/images/bio-images-iaaf/bio-moore.jpg deleted file mode 100644 index e1fffdfd1..000000000 Binary files a/assets/images/bio-images-iaaf/bio-moore.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-nielson.jpg b/assets/images/bio-images-iaaf/bio-nielson.jpg deleted file mode 100644 index f143b98a6..000000000 Binary files a/assets/images/bio-images-iaaf/bio-nielson.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-paschel.jpg b/assets/images/bio-images-iaaf/bio-paschel.jpg deleted file mode 100644 index 5dae08505..000000000 Binary files a/assets/images/bio-images-iaaf/bio-paschel.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-peters.jpg b/assets/images/bio-images-iaaf/bio-peters.jpg deleted file mode 100644 index 9ac364d0c..000000000 Binary files a/assets/images/bio-images-iaaf/bio-peters.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-pomeroy.jpg b/assets/images/bio-images-iaaf/bio-pomeroy.jpg deleted file mode 100644 index 847cc5fb4..000000000 Binary files a/assets/images/bio-images-iaaf/bio-pomeroy.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-prabhakaran.jpg b/assets/images/bio-images-iaaf/bio-prabhakaran.jpg deleted file mode 100644 index 8a9638dc0..000000000 Binary files a/assets/images/bio-images-iaaf/bio-prabhakaran.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-pruitt.jpg b/assets/images/bio-images-iaaf/bio-pruitt.jpg deleted file mode 100644 index e4cec5c45..000000000 Binary files a/assets/images/bio-images-iaaf/bio-pruitt.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-robertson.jpg b/assets/images/bio-images-iaaf/bio-robertson.jpg deleted file mode 100644 index 85480500a..000000000 Binary files a/assets/images/bio-images-iaaf/bio-robertson.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-ryan.jpg b/assets/images/bio-images-iaaf/bio-ryan.jpg deleted file mode 100644 index c92103903..000000000 Binary files a/assets/images/bio-images-iaaf/bio-ryan.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-salmoiraghi.jpg b/assets/images/bio-images-iaaf/bio-salmoiraghi.jpg deleted file mode 100644 index 1fb4c0b6e..000000000 Binary files a/assets/images/bio-images-iaaf/bio-salmoiraghi.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-schell.jpg b/assets/images/bio-images-iaaf/bio-schell.jpg deleted file mode 100644 index 529ad6d8f..000000000 Binary files a/assets/images/bio-images-iaaf/bio-schell.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-schweickhardt.jpg b/assets/images/bio-images-iaaf/bio-schweickhardt.jpg deleted file mode 100644 index 3926dc028..000000000 Binary files a/assets/images/bio-images-iaaf/bio-schweickhardt.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-sharma.jpg b/assets/images/bio-images-iaaf/bio-sharma.jpg deleted file mode 100644 index 1639a89f9..000000000 Binary files a/assets/images/bio-images-iaaf/bio-sharma.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-singleton.jpg b/assets/images/bio-images-iaaf/bio-singleton.jpg deleted file mode 100644 index 8f21d441d..000000000 Binary files a/assets/images/bio-images-iaaf/bio-singleton.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-sirk.jpg b/assets/images/bio-images-iaaf/bio-sirk.jpg deleted file mode 100644 index cca09c615..000000000 Binary files a/assets/images/bio-images-iaaf/bio-sirk.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-sullivan.jpg b/assets/images/bio-images-iaaf/bio-sullivan.jpg deleted file mode 100644 index fadf4f460..000000000 Binary files a/assets/images/bio-images-iaaf/bio-sullivan.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-thurston.jpg b/assets/images/bio-images-iaaf/bio-thurston.jpg deleted file mode 100644 index 54b5c8f44..000000000 Binary files a/assets/images/bio-images-iaaf/bio-thurston.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-truesdell.jpg b/assets/images/bio-images-iaaf/bio-truesdell.jpg deleted file mode 100644 index 564e3131d..000000000 Binary files a/assets/images/bio-images-iaaf/bio-truesdell.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-urban.jpg b/assets/images/bio-images-iaaf/bio-urban.jpg deleted file mode 100644 index 4854d15d3..000000000 Binary files a/assets/images/bio-images-iaaf/bio-urban.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-vanderheiden.jpg b/assets/images/bio-images-iaaf/bio-vanderheiden.jpg deleted file mode 100644 index 3fd83ca80..000000000 Binary files a/assets/images/bio-images-iaaf/bio-vanderheiden.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-whittington.jpg b/assets/images/bio-images-iaaf/bio-whittington.jpg deleted file mode 100644 index 7a97ffa50..000000000 Binary files a/assets/images/bio-images-iaaf/bio-whittington.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-williams.jpg b/assets/images/bio-images-iaaf/bio-williams.jpg deleted file mode 100644 index 85dcaaddd..000000000 Binary files a/assets/images/bio-images-iaaf/bio-williams.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-willie-smith.jpg b/assets/images/bio-images-iaaf/bio-willie-smith.jpg deleted file mode 100644 index d9f686d34..000000000 Binary files a/assets/images/bio-images-iaaf/bio-willie-smith.jpg and /dev/null differ diff --git a/assets/images/bio-images-iaaf/bio-ziebarth.jpg b/assets/images/bio-images-iaaf/bio-ziebarth.jpg deleted file mode 100644 index 7e4080027..000000000 Binary files a/assets/images/bio-images-iaaf/bio-ziebarth.jpg and /dev/null differ