Accessibility review

In light of the great success of the Umbraco Accessibility Team, I’d like for Contentment to pull it’s own weight and ensure that the same principles have been applied.

I’ve tried to make efforts to ensure accessibility, e.g. use of <button>, ARIA, labelling, etc. But I’m never sure it is truly accessible. It’d be great to have help with accessibility concerns. I’d love to learn something too.

Background reading

• https://our.umbraco.com/forum/contributing-to-umbraco-cms/96398-call-for-an-accessibility-team
• https://github.com/umbraco/Umbraco-CMS/issues/5277
• https://trello.com/b/7M8RosrE/umbraco-accessiblity-issues-84

Feedback, expectations and Hackotoberfest

Whilst code patches are hugely appreciated, my expectation for collaboration on any accessibility review is more about raising issues for feedback. My hope is to highlight any accessibility issues that even seasoned developers can mistake.

Pull Requests (so far) …

• #45 ContentBlocksOverlay: Various changes (thx @BatJan)
• #44 ConfigurationEditorOverlay: Make use of Umbraco directives and change <a> to <button> (thx @BatJan)
• ba20147c0efffc1561c3e4d564904b955387c05c ItemPicker overlay - change <a> to <button> (me, @leekelleher)

[greystate]

No problem @leekelleher

@zersiax Throw me an email at chriztian[at]steinmeier.dk and I’ll invite you to the site.

[greystate]

@leekelleher @zersiax I can set one up w/ v1.0.1 and provide access, no problem.