{"id":15542808,"url":"https://github.com/melsumner/a11y-failures-json","last_synced_at":"2026-02-12T10:02:04.209Z","repository":{"id":78400848,"uuid":"293829464","full_name":"MelSumner/a11y-failures-json","owner":"MelSumner","description":"Itemized way that web-based apps and related developer tooling could fail accessibility criteria","archived":false,"fork":false,"pushed_at":"2020-09-10T14:41:46.000Z","size":9,"stargazers_count":1,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"main","last_synced_at":"2025-08-16T18:35:36.262Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/MelSumner.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2020-09-08T14:08:39.000Z","updated_at":"2024-07-01T05:38:02.000Z","dependencies_parsed_at":"2023-03-28T23:24:38.376Z","dependency_job_id":null,"html_url":"https://github.com/MelSumner/a11y-failures-json","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/MelSumner/a11y-failures-json","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MelSumner%2Fa11y-failures-json","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MelSumner%2Fa11y-failures-json/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MelSumner%2Fa11y-failures-json/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MelSumner%2Fa11y-failures-json/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/MelSumner","download_url":"https://codeload.github.com/MelSumner/a11y-failures-json/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MelSumner%2Fa11y-failures-json/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29363010,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-12T08:51:36.827Z","status":"ssl_error","status_checked_at":"2026-02-12T08:51:26.849Z","response_time":55,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-02T12:24:35.359Z","updated_at":"2026-02-12T10:02:04.171Z","avatar_url":"https://github.com/MelSumner.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Accessibility Failures\n\nThis is a JSON file that attempts to aggregate and uniformly itemize all of the mechanisms by which websites, web-based applications, and their associated developer tools can lead to failures in achieving known accessibility success criteria. \n\nCurrently, a single data source that contains all of this information does not exist. In principle, the completed dataset provides a much-needed consolidation of web accessibility failure reference information, and could be used for any number of custom applications (to track issues, guide accessibility engineering work, create new tooling, etc).\n\nNOTE: This is currently a work in progress!\n\n## Technical Details\n\nFor each itemized criteria, the following information is provided: \n\n* id (string; auto-incremented number)\n* criteria (array; WCAG, EN or Section 508 reference(s))\n* description (string; short descriptor of issue)\n* help (string; advice on how to fix the issue described)\n* severity (string; should be single value of blocker, critical, major or minor (outlined below))\n* tags (array; should be logical and consistent with the others)\n* testing (array; can have multiple values (outlined below))\n\n### References used \n\n* [WCAG 2.1](https://www.w3.org/TR/WCAG21/)\n* [ARIA Role documentation](https://www.w3.org/WAI/PF/aria/roles)\n* [WCAG Techniques](https://www.w3.org/WAI/WCAG21/Techniques/#techniques)\n* [EN 301 549](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/02.01.02_60/en_301549v020102p.pdf)\n* [Section 508](https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/single-file-version)\n* [axe-core](https://github.com/dequelabs/axe-core/tree/develop/lib/rules) (has several \"best practices\" outlined)\n\n### Severity levels\n\nWhile a page's conformance is a pass or fail, giving itemized failures a severity level can help prioritize work. All issues, no matter what their severity, must be resolved for a page to be conformant.\n\n* Blocker - Complete loss of service, critical functionality, or data with no acceptable workaround. Includes significant privacy and security risks\n* Critical - Severe degradation of critical functionality or data; functionality is still available but is severely limited.  No acceptable workaround is available, but use is still possible in a restricted fashion\n* Major - Loss of critical functionality or data, but there is a reasonable workaround available\n* Minor - Loss or degradation of non-critical functionality or data.  A workaround may or may not be available\n\n### Testing\n\nFor each failure item, it should be determined how the item can be tested. Options are:\n\n1. it can be linted for\n2. it has/can have an automated test\n3. a developer must write the test\n4. it must be manually tested for\n\n## Contributing to this repository\n\nContributions are welcome. To contribute, please follow these steps: \n\n1. file an issue on the repository that outlines the missing itemization and links to the relevant success criteria.\n2. submit a PR that addresses that issue (and only that issue)\n\nPolite language is expected.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmelsumner%2Fa11y-failures-json","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmelsumner%2Fa11y-failures-json","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmelsumner%2Fa11y-failures-json/lists"}