A new feature for SilverStripe should be ...

Accessibiility compliance in CMS

Ensure that less able CMS authors can work with our core toolset.

- Follow guidance of the W3C for Rich Internet Applications (ARIA): https://www.w3.org/WAI/intro/aria
- Follow guidance of the W3C for Authoring Tools (ATAG): https://www.w3.org/WAI/intro/atag

Notes:
- WCAG compliance is often mandated in tools used by government. See Australia (https://www.dta.gov.au/standard/9-make-it-accessible/) or New Zealand (https://webtoolkit.govt.nz/standards/web-accessibility-standard-1-0/) for examples.

21 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Pav Singh shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Ingo Schommer responded  · 

    I’ve broadened this idea from ATAG compliance to wider “accessibility compliance” in the CMS.

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • AdminIngo Schommer (Admin, SilverStripe) commented  ·   ·  Flag as inappropriate

        Could you refer to any govt policy documents which mandate or favour ATAG compliant CMS? Do you have an example of a compliant CMS? I'm always interested in making the CMS more accessible, but fear that without external funding or a commercial business case other features will take precedence (sadly).

        We're already reasonably accessible (document structure, link targets, titles, jQuery UI modals), but need to do better in declaring content areas, hierarchical structures like the tree, dropdowns, and announcing ajax updates appropriately,

      Feedback and Knowledge Base