From b2a6c379c68d29d01dbe2aec170c6757387761ee Mon Sep 17 00:00:00 2001 From: Michael Horton Date: Wed, 18 Dec 2024 09:19:15 -0500 Subject: [PATCH] Bug fixes from feb 2023 --- _data/sidenav.yaml | 2 - _pages/acquisition/2018-05-29-sell-acr.md | 1 - ...manage-improve-digital-dashboard-scores.md | 143 ------------------ 3 files changed, 146 deletions(-) delete mode 100644 _pages/manage/2020-10-22-manage-improve-digital-dashboard-scores.md diff --git a/_data/sidenav.yaml b/_data/sidenav.yaml index ac12b8c87..ab1c1f30b 100644 --- a/_data/sidenav.yaml +++ b/_data/sidenav.yaml @@ -13,8 +13,6 @@ manage: grandchildren: - name: Accessibility Roles url: manage/roles/ - - name: Improve Digital Dashboard Accessibility Scores - url: manage/improve-digital-dashboard-scores/ - name: Publish Accessible Content url: manage/publish-accessible-content/ - name: Teach Staff about Accessibility diff --git a/_pages/acquisition/2018-05-29-sell-acr.md b/_pages/acquisition/2018-05-29-sell-acr.md index 90af88436..1327782d1 100644 --- a/_pages/acquisition/2018-05-29-sell-acr.md +++ b/_pages/acquisition/2018-05-29-sell-acr.md @@ -35,7 +35,6 @@ We recommend that vendors generate an ACR for any ICT that's intended to be mark * [Request Accessibility Information from Vendors and Contractors][4] - Guidance for agencies on how to develop and document accessibility requirements * Introducing VPAT® 2.0, the More Stringent Accessibility Reporting Tool Required for Government IT Procurement * [Demystifying Section 508: An Industry Guide to Understanding Section 508 of the Rehabilitation Act][5] (PDF) | NASA - * Navigating VPAT® 2.0: A Guide for Vendors * Win More Business! Report Product & Service Accessibility using VPAT® 2.1 (MS PPT, March 2018) **Reviewed/Updated**: April 2024 diff --git a/_pages/manage/2020-10-22-manage-improve-digital-dashboard-scores.md b/_pages/manage/2020-10-22-manage-improve-digital-dashboard-scores.md deleted file mode 100644 index 50754a4b3..000000000 --- a/_pages/manage/2020-10-22-manage-improve-digital-dashboard-scores.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -layout: page -sidenav: true -permalink: manage/improve-digital-dashboard-scores/ -type: manage -title: "How to Improve Digital Dashboard Accessibility Scores" -created: 1603390069 -topic: "Manage (program)" -sub-topic: "Manage a 508 Program" -audience: -- "508 Program Manager (508pm)" -- "Agency Head (head)" -- "Chief Information Officer (cio)" -- "Information Technology Program and Project Managers (itpm)" -- "Lawmakers and Policy Officials (law-policy)" -resource-type: "Process/How-to" -format: "HTML (html)" ---- - -In order to improve your agency’s website accessibility scores within the Digital Dashboard tool, we must understand why we test, how tests are conducted, and the limitations of automated testing. The below guidance is intended to assist with improving website scores on the Digital Dashboard Accessibility module. For other Digital Dashboard questions, please visit the [frequently asked questions][1] on [DigitalDashboard.gov][2]. - -- [Section 508 Accessibility Standards][3] -- [How Websites are Measured][4] -- [Limitations to Automated Testing][5] -- [How to Fix Accessibility Issues][6] -- [How to Access the Digital Dashboard][7] -- [Related Resources][8] - ---- - -

- Section 508 Accessibility Standards -

- -In 1998, Section 508 of the Rehabilitation Act of 1973 was amended to require all federal agencies to make their electronic and communications technology accessible to people with disabilities. In 2017, the U.S. Access Board issued Revised Section 508 Standards which, in part, harmonize Section 508 requirements with other guidelines and standards both in the U.S. and abroad, including standards issued by the European Commission and as well as the standards set forth by the Web Content Accessibility Guidelines (WCAG), a globally recognized voluntary consensus standard for web content and ICT. - -For additional information on Section 508 standards, laws and associated requirements, visit: - - -

- How Websites are Measured -

- -### The Tool - -The data presented by the Accessibility module is obtained through use of an open-source application known as [Pa11y][16]. Pa11y uses other open-source tools, including HTML_Codesniffer and aXe Core, to identify accessibility issues.  - -While we selected Pa11y to scan for accessibility issues presented by the Accessibility Module, there are a range of other proprietary and open-source tools available to assist web developers and IT managers in creating accessible technology. It is recommended that agencies ensure their automated and manual accessibility testing tools and processes align with the [ICT Testing Baseline][17].  - -### The Findings  - -The Digital Dashboard’s Accessibility module scans for certain common accessibility issues across all publicly accessible .gov executive branch agency websites. Website domains that simply redirect to other websites are not measured. The Accessibility module scans second-level federal .gov websites (e.g., agency.gov). Note that third-level federal websites, such as program.agency.gov, .mil, .edu, .us, and state, local, and Native Sovereign Nation (NSN) are not currently scanned by the Accessibility module. - -The Accessibility Module performs spot checks, informed by the current Section 508 standards. The checks use the WCAG 2.0 success criteria associated with each standard to inform the testing approach. For test rule details, visit [Digital Dashboard Accessibility Guidance][18]. - -

- Limitations of Automated Testing -

- -

- All automated testing, including that performed by the Digital Dashboard’s Accessibility module, is limited to programmatic conformance testing. Automation can test some, but not all, of the technical requirements. For example, while automated tools may be able to identify whether or not an image has an ALT attribute (and whether that attribute is blank or has a text value), they are currently unable to determine if that ALT text is a meaningful or equivalent description of the image. As such, the Accessibility module reports do not constitute a complete accessibility evaluation and must be accompanied by manual inspection. Agencies should use both automated and manual testing (conducted by a certified tester) to fully assess whether their website is accessible. For additional testing guidance, visit Accessibility Testing for Software and Websites.  -

- -

- How to Fix Accessibility Issues -

- -

- The tools listed above provide web developers and content managers with the information they need to pinpoint issues on their pages. While some issues may involve a more significant overhaul of a website’s architecture, most can be corrected with only minor updates to the site, such as deleting errant tags, making minor CSS adjustments, or adding ALT text to images. -

- -

- Technical Guidance: -

- - * [Guide to Accessible Web Design & Development][11] - A guide on relevant Web Content Accessibility Guidelines (WCAG) requirements with specific considerations for content, design, and development. - * [How to Meet WCAG (Quick Reference)][15] - A customizable quick reference to Web Content Accessibility Guidelines (WCAG) 2.0 requirements (success criteria) and techniques. -

- If you need help fixing issues identified in the Accessibility module, contact your agency’s Section 508 Program Manager, or our team at section.508@gsa.gov. -

- -

- How to Access the Digital Dashboard -

- -

- To access the Digital Dashboard Accessibility Module, simply:  -

- -
    -
  1. - Sign into DigitalDashboard.gov using your MAX.gov account
    2. -
  2. - Select the “Accessibility” module link, and review the data for your agency. -
    3. -
- -

- Note: First-time dashboard users will need to submit a one-time request to dotgovdashboard@gsa.gov for access to your agency data. -

- -

Related Resources

- -
-
-

Before You Go

-

We're always working to improve the information and resources on this website. To suggest a new resource for this or another page, please contact us -.

-
-
-

Reviewed/Updated: November 2022

- -[1]: https://www.digitaldashboard.gov/index.php/?check_logged_in=1 -[2]: https://www.digitaldashboard.gov -[3]: #standards -[4]: #measure -[5]: #limits -[6]: #fix -[7]: #dashboard -[8]: #resources -[9]: {{site.baseurl}}/manage/laws-and-policies -[10]: {{site.baseurl}}/test/web-software -[11]: {{site.baseurl}}/content/guide-accessible-web-design-development -[12]: {{site.baseurl}}/content/mapping-wcag-to-fpc -[13]: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh -[14]: https://www.w3.org/TR/WCAG20/ -[15]: https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0¤tsidebar=%23col_overview&levels=aaa#principle1 -[16]: https://pa11y.org/ -[17]: https://section508coordinators.github.io/ICTTestingBaseline/ -[18]: https://www.digitaldashboard.gov/content/accessibility-guidance \ No newline at end of file