No screen reader testing, since here you set the color scheme and fonts for the skin. Vision seems to be a requirement to accomplish this.
|-
| style="width:80px;"|CF
| style="width:220px;" | HitCounters
| style="width:100px;" |
|
|
|-
|-
| style="width:80px;"|CF
| style="width:80px;"|CF
| style="width:220px;" | InputBox
| style="width:220px;" | InputBox
| style="width:100px;" |
|
|
|-
| style="width:80px;"|CF
| style="width:220px;" | Interwiki
| style="width:100px;" |
| style="width:100px;" |
|
|
Line 308:
Line 158:
|
|
|
|
|-
| style="width:80px;"|CF
| style="width:220px;" | Math
| style="width:100px;" |AT, Web
|'''<span class="col-red">FAIL</span>'''
|'''<span class="col-red">FAIL</span>''' is okay here, this type of image output is simply not supported by screenreaders. ''workaround: maybe MathML-based syntax?''
|-
|-
| style="width:80px;"|CF
| style="width:80px;"|CF
Line 335:
Line 179:
| style="width:80px;"|CF
| style="width:80px;"|CF
| style="width:220px;" | Nuke
| style="width:220px;" | Nuke
| style="width:100px;" |
|
|
|-
| style="width:80px;"|CF
| style="width:220px;" | Page Schemas
| style="width:100px;" |
| style="width:100px;" |
|
|
Line 350:
Line 188:
|'''<span class="col-red">FAIL</span>'''
|'''<span class="col-red">FAIL</span>'''
|needs aria labels, screenreader doesn't read them out
|needs aria labels, screenreader doesn't read them out
|-
| style="width:80px;"| CF
| style="width:220px;" | Replace Text
| style="width:100px;" |
|
|
|-
| style="width:80px;"|CF
| style="width:220px;" | RSS
| style="width:100px;" |
|
|
|-
|-
| style="width:80px;"|CF
| style="width:80px;"|CF
Line 395:
Line 221:
!WCAG
!WCAG
!Accessibility notes
!Accessibility notes
|-
| |n/a
| class="col-grey-light-bg" |Auth remoteuser
| class="col-grey-light-bg" |n/a
| class="col-grey-light-bg" |
| class="col-grey-light-bg" |
|-
| |CF
|BlueSpiceCategoryManager
|AT, Web
|partially supported
|supported: tabbing through tabular data
not supported:
*Extjs: Pagination in grids not announcing button types and spinbutton value
*parent-child relationships not announced
*actions-buttons only visible and interactive on mouse-hover
workaround: categories can also be managed directly on the category pages themselves. The parent-child relationship of categories is also always listed on the categories pages
|Note: This extension allows to use various CAPTCHA techniques. To comply, an accessible captchas (e.g. ReCaptcha or hCaptcha) would have to be implemented and techniques [https://www.w3.org/WAI/WCAG21/Techniques/general/G143.html G143] AND [https://www.w3.org/WAI/WCAG21/Techniques/general/G144.html G144] need to be applied.
|-
| |n/a
| class="col-grey-light-bg" |EditNotify
|
|
| class="col-grey-light-bg" |
|-
|-
| |n/a
| |n/a
Line 578:
Line 269:
|
|
| class="col-grey-light-bg" |
| class="col-grey-light-bg" |
|-
| |CF
|FlexiSkin
|AT
|'''FAIL'''
(easy fix)
|Small keyboard access issues [[erm:25223]]
No screen reader testing, since here you set the color scheme and fonts for the skin. Vision seems to be a requirement to accomplish this.
While using BlueSpice, turn off High Contrast mode and switch to the Color filter setting instead. Here, you also get a hight contrast setting in black, but the Visual Editor toolbar is fully visible:
All functionality of VisualEditor can be entered in source editing mode, which is a standard way of editing a wiki page. The save dialog can be activated via keyboard alt+shift+s. Available Shortcut keys can be viewed with Ctrl+/
Extended functionality
TemplateData
Does not support
dialog window does not recognize language
no tabbing to hidden fields (solution: user task: mark all non-required fields as suggested to be shown instantly).