Andrew Macpherson

The thing I'd like to do is replace the colon which appears before the column number. Airline provides ` g:airline_symbols.linenr` and ` g:airline_symbols.maxlinenr`, but no way to customize what appears...

I don't think `aria-label` is the most flexible or inclusive approach here. The problem with `aria-label` is that it it's invisible, and *only* conveys the input purpose to (some) assistive...

Terminology clarification: in WCAG, "label" refers to the *visible* name of a control. Neither `aria-label` nor `aria-labelledby` provide that. In the screenshot on this project's README, there is no visible...

``` mark { box-sizing: border-box; border: 1px dotted transparent; } ``` This is VERY likely to be confused with the default focus style in Firefox + IE, which is a...

@TLyngeJ There's a typo in a comment. `Uncomment the followinf line` => `Uncomment the following line`

@thejohnnyhill `role="text"` isn't appropriate, because: 1. The `role` attribute _overrides_ the native semantics of the element it is applied to. If splitting.js applies `role="text"` as a generic approach, it will...

@shshaw > Still working through some approaches and seeking feedback on the best way to make screenreaders ignore these decorative elements since aria-role="presentation" doesn't seem to do it properly. You've...

Using `aria-hidden="true"` on the generated spans is a good idea, so long as the text is presented by another method. Using `aria-label` on the elements being split isn't going to...

An alternative approach to `aria-label` is to use a visually-hidden span as the accessible text. This is quite a robust approach to providing accessible text alternatives. e.g. `ACME` is transformed...

This find out more link is hard to spot. The arrow head technically passes SC 1.4.1 Use of Color, but unless you are reading the text it just gets lost...