Much of accessibility issues are in the hands of the authors. Documentation on making accessible content could be provided below textareas and wysiwygs edit areas.

Comments

johnbarclay’s picture

Title: Add helpful accessibility links/tips in textareas » Add validator for accessibile text in text areas

Perhaps the code from the functional accessibility evaluator or other accessibility tools could be used to validate text content. Admins could enable/disable the feature and determine if validation was a must or validation simply produced warnings.

johnbarclay’s picture

Version: » 6.x-1.x-dev
kat3_drx’s picture

Assigned: Unassigned » kat3_drx

If no one minds, I'm going to try a hook to scan for char limits, line breaks, h1-h6 headings, things like that in content text, before publishing or revisions.

johnbarclay’s picture

Sounds good.

Anonymous’s picture

Much of this functionality is available in Accessible Content for node edit forms; however, it does not hook into any textareas that are found in admin interfaces, etc. I think it might make sense that this functionality reside in Accessible Helper - maybe you could have an admin setting to set a site-wide default guideline (from the accessible content guideline nodes) and then just use accessible_content_check_string() to check content on form submit.

johnbarclay’s picture

Seems reasonable. I think it would make more sense to keep such functionality in accessible content. Do you not want it there? I would like see how the accessible content module could be used as an api and this is a great example case.

mgifford’s picture

Version: 6.x-1.x-dev » 7.x-3.x-dev
Issue summary: View changes
Issue tags: +atag
mgifford’s picture

We might be able to include this as a duplicate #2731373: [upstream] Include an accessibility tester in CKEditor (axe, Tota11y, HTML Code Sniffer)

That is unless we want to either support other WYSIWYG editors...

mgifford’s picture