Accessibility: WCAG 2.1 AA Compliance.
(UXPROD-216)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Accessibility: WCAG 2.1 AA Compliance. |
| Type: | Story | Priority: | TBD |
| Reporter: | Julian Ladisch | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | NFR, a11y, accessibility, ui-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Accessibility: WCAG 2.1 AA Compliance. |
| Development Team: | None |
| PO Rank: | 0 |
| Description |
|
"provide and regularly update a detailed, comprehensive and clear accessibility statement on the compliance" EU law requires public sector bodies to conduct a comprehensive accessibility review for the accessibility statement: Directive EU 2016/2102 Article 7: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016L2102&from=EN The requirements are
How frequent is "regularly update"? At least yearly in Lower Saxony: § 4 (6) NBITVO https://www.nds-voris.de/jportal/?quelle=jlink&query=BITV+ND&psml=bsvorisprod.psml&max=true&aiz=true Is there an example? Yes:
|
| Comments |
| Comment by Khalilah Gambrell [ 28/Sep/21 ] |
|
Julian Ladisch is this something that GBV can take the lead? |