Note that there are some explanatory texts on larger screens.

plurals
  1. POAccessibility: How to mark up information conveyed only by colour accessibly?
    primarykey
    data
    text
    <p>I am working on a web application that offers, essentially, Diff for legal documents. That is, it can show changes to legal documents over time in a similar way to a graphical Diff utility.</p> <p><img src="https://i.stack.imgur.com/8d7vx.gif" alt="Example of colour coding"></p> <p>It uses a wide range of text styles, more than my example - at least 3 colours, and strikethrough - to convey meaning. I'd like advice about how to implement this as accessibly as possible. The markup will probably be fairly unsemantic, something like </p> <pre><code>&lt;span class="col-repealed"&gt;The Commissioners before whom an appeal under this section is brought&lt;/span&gt; &lt;span class="col-inserted"&gt;On an appeal that is notified to the tribunal&lt;/span&gt;, the tribunal must consider whether the registration of the pension scheme ought to have been withdrawn. </code></pre> <p>I will be testing with colour blindness simulators to ensure the colours are all adequately differentiatible. I am also planning to create a black-and-white print stylesheet (where I'd probably change colours to various underline or outline styles, and also print a key to the styles.)</p> <p>I'm wondering about users of screen readers though. I believe this calls for an aural stylesheet, with different voices standing in for different colours. I've never done aural stylesheets before. Are they well enough supported to be worth the effort? Are there other things I could or should do? (E.g. title attributes on the spans)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload