Skip to content

Use cases

Charles LaPierre edited this page Jan 4, 2019 · 60 revisions

Background Information

This page is for creating use cases to test if different proposals for implementing the vocabularies can work

Each use case should have a description, link to the requirement or easy language requirement and two code examples. Code example should include the AUI attributes and an example with the minim attributes possible.

links:

Summary

  • one can do a single attribute for may tokens if they are able to be separated with whitespace. In real life they have been shown to be confusing (by implementors- who do not always read and understand every word in the specification) as the context is not clear
  • **a single attribute for may text values: **would require a very complex data model if it is even possible - all the disadvantages of value pairs come into play
  • **a single attribute for may uri value: **would require a very complex data model if it is even possible- all the disadvantages of value pairs come into play

Stories

Easily Distracted / Overwhelmed

Someone who is either easily distracted or can be easily overwhelmed with too much information on a web page needs the ability to simplify the page to just the critical information and suppress anything that is not integral to the understanding and use of the page.

Example #1: You want to get the latest weather report for your city and go to www.weather.com website. Finding the actual weather forecast is actually a little challenging even if you have no disabilities. In addition to all the ads above, beside and below the information you actually want, there is also todays top stories, trending news, and social media to ignore. If you are easily overwhelmed or distracted getting the key information about the weather for today is a challenge. Having the ability to personalize and strip away all but the key information i.e. just the weather forecast for my city is critical for this person.

In this example the author of this webpage would mark the <section>, <p>, or <div> that contains the actual weather report and any associated the tools to manipulate the weather report (i.e. city search, hourly vs. 5 day forecast, etc.) as simplification=critical, and mark the other content as medium or low.

Difficulty understanding Numbers

Someone who has dyscalculia and therefore has difficulty understanding numbers will have a hard time with any website that uses numbers to convey information. This numeric information must be provided in an alternative format that the user can understand.

Example #2: You want to get the latest weather report for your city and go to www.weather.com website. For today’s forecast it shows a high of 95℉ and a low of 40℉, which is not helpful for this particular user. Allowing this numeric information to be presented instead as an image or symbol would benefit the user. I.e. instead of 95℉ a picture of someone wearing shorts and a tee shirt with the sun above, and instead of 40℉ a picture of someone wearing a jacket with pants.

In this example the author would have the numbers marked up in using numberfree where the default would show the numeric value but for those needing an alternative representation for numbers would get an associated image or description to be presented instead.

Severe Speech and Physical Impairment

Those who have a severe speech and physical impairment the use of symbols to represent words is their primary means of communication. The ability to personalize a webpage and present symbols instead can help those easily understand the content being provided.

Example: Marking up the Home button and allowing for the Bliss Symbol for “Home Page”
will help this user better navigate the website.

In this example the author would add symbol=”uri to the symbol for homepage” or maybe a href to an image file.


Single issue Use Cases

Simplification

Use case: The user would prefer to see only the critical information and required fields to complete a task.

Original

<div>
  <form action="#" method="post"><br /> 
    <p>Enter your e-mail address to subscribe to our mailing list.</p><br /> 
    <label for="address">Enter email address:</label>
    <input type="text" id="address" name="address"/></p><br />
    <input type="submit" value="Subscribe" />
  </form>
</div>

AUI Attributes

<div>
  <form action="#" method="post"><br /> 
    <p>Note: [*]denotes mandatory field</p>
    <p>Enter your e-mail address to subscribe to our mailing list.</p><br /> 
    <label for="address">Enter email address:</label>
    <input type="text" id="address" name="address" aui-field="email" aui-simplification="critical" aria- 
    required="true"/>[*]</p><br />
    <input type="submit" aui-simplification="critical" value="Subscribe" />
    <br /> 
  </form>
</div>

#Two token use cases

Simplification and field

Use case: The user would prefer to see only the critical information and required fields to complete a task.

Original b

<div>
  <button id="1">send</button>
  <button id="2">undo</button>
  <button id="3">lable</button>
  <button id="4">send later</button>
  <button id="5">mark urgentr</button>
</div>

AUI Attributes - b

<div>
  <input type="submit" aui-simplification="critical" aui-action="send" value="send" />
  <button id="2" aui-simplification="high" aui-action="undo">undo</button>
  <button id="3" aui-simplification="normal">lable</button>
  <button id="4" aui-simplification="normal">send later</button>
  <button id="5" aui-simplification="normal" >mark urgentr</button>
</div>

3 Attributes - b

<div>
  <input type="submit" context ="critical send" value="send" />
  <button id="2" context="high undo">undo</button>
  <button id="3" context="normal">lable</button>
  <button id="4" context="normal">send later</button>
  <button id="5" context="normal" >mark urgentr</button>
</div>

Content Filtering (inception)

User may have sensitivity to certain words or topics; based on personal preference, culture or disability which are expressed on a page using text, images or video.

Given one or more strings representing a specified word or category, for example, content marked as explicit, violent, etc., hide or remove that string and associated elements from the DOM.

  • aui-action = hide
  • URI = JSON file of words

Consideration: How are we bringing in data sets to support use cases that depend on external data, for example, symbols or simple language vocabularies? Is this through separate JS or is the vision to have that abstracted by the implementation.

Alternative (by lisa) aui-trigers = list of words

at the user end the content will be hiden under a warning button if any of the words match a word idendetifed as a tiger in the user prefrences

for example aui-trigers = "violent rape"


Two text field Use Cases

Numberfree and extrahelp

This example proved much harder to create than I expected. I will admit that I am still confused at how to create the examples and am not confident that these are correct. I also intended to have this be an example that needed two types of replacement but when I implemented it, I realized I could split it into two separate substitutions. becky

The user needs content that does not use numbers and needs extra help and information to complete a task.

Original

<div>
     7 out of 10 people order pizza with some kind of meat topping. 
     Select the toppings below in order of preference that you would 
     order on pizza.
</div>
<form>
  sophisticated form to select/rank pizza toppings in order of preference
</form>

3 Attributes

<div>
   <span context="numberfree" easylang="most people">
       7 out of 10 people
   </span> 
   order pizza with some kind of meat topping. 
   <span context="extrahelp" reference="href-to-simplifiedInstructions">
       Select the toppings below in order of preference that you would order on pizza.
   </span>
</div>

AUI Attributes

<div>
  <span aui-numberfree="Most people">
     7 out of 10 people
  </span> 
  order pizza with some kind of meat topping. 
  <span aui-extrahelp="href-to-simplifiedInstructions">
     Select the toppings below in order of preference that 
     you would order on pizza.
  </span>
</div>

Numberfree and easylang

Use case: The user prefers alternative text that does not use numerical concepts as well content that is easier to read and understand.

Original

<p>
   Comparing the present clock-reported time which is 5 minutes
   after 09:00 AM with what we previously discussed 
   yesterday, and made an agreement about, 
   it seems that I myself may not be exactly on schedule
</p>

AUI Attributes

<div>
    <span easylang="I'm running late">
        Comparing the present clock-reported time which is 
        <span aui-numberfree="midmorning">
           5 minutes after 09:00 AM
        </span> 
        with what we previously discussed 
        yesterday, and made an agreement about, it seems that 
        I myself may not be exactly on schedule
    </span>
</div>

Numberfree and easylang 2

Use case: we have two use cases

A. The user prefers alternative text that is easy to read and understand but is good with numbers (eg dyslexic)

Original 2.a

<p>
   Comparing the present clock-reported time 
   you many wish to come a bit later than the normal time.
</p>

AUI Attributes 2.a.1

<div>
  <span aui-easylang="come to the meeting at 9:10">
       Comparing the present clock-reported time you many wish 
       to come a bit later then the normal time
  </span> 
</div>

three attribute 2.a.2

<div>
    <span easylang="come to the meeting at 9:10">
        Comparing the present clock-reported time 
        you many wish to come a bit later then the normal time
    </span> 
</div>

B: the user can understand words well but has dyscalculia and does not understand numbers

Original 2.b

<p>
  meeting is starting 10 minutes late
</p>

AUI Attributes 2.b.1

<div>
   <span aui-easylang="come a bit later then the normal time - enough time for a cup of tea... ">
      meeting is starting 10 minutes late
   </span> 
</div>

three attribute 2.b.2

<div>
  <span easylang="come a bit later then the normal time - enough time for a cup of tea... " context="numbers">
     meeting is starting 10 minuets late
  </span> 
</div>

Three text fields usecases

feedback, explain and easy lang

Use case: The user needs

  • easy language and
  • a bit more information about how the interface works
  • what just happened - i.e. did they need to click something else, did it work?

In this example search criteria in one part of a page controls the results in anther region which showes the side effects of a drug. Other buttons may show dosage etc in the results region

Original

<input  
  aui-context ="critical" value="refresh" aria-controls="region2" 
/>

aui-

<input  aui-simplification="critical"  
  aui-feedback="the results now are for ibuprofen side effect" 
  value="refresh" 
  aria-controls="region2" 
  aui-easyLang="get the side effects" 
  aui-explain="press this button to see the side effects of a drug"  
/>

3 Attributes

I could not do this in three attributes. So I did what I could

<input  
   context="critical" 
   aui-feedback="the results now are for ibuprofen side effect" 
   value="refresh" 
   aria-controls="region2" 
   aui-easyLang="get the side effects" 
   aui-explain="press this button to see the side effects of a drug"  
/>

more then one URI use case

symbol and extra help

Use case: The user needs

  • symbols
  • extra text and help

Original

<div>
  <strong>warning</strong> 
  in the event of a siren go to the designated protected area
</div>

aui-

<div>
  <strong region="warning">warning</strong> 
  <span aui-symbol="blis.org/syrin"> in the event of a siren </span>
  <span aui-symbol="blis.org/goto"> go to </span>
  <span aui-symbol="blis.org/shelta" 
    aui-extrahelp=mysite/whatisashelter-easylang.html">the designated protected area
  </span>
</div>

three attibutes

I could not do it in three

this is the best I can do

warning in the event of a siren
go to <span reference="blis.org/shelta" extrahelp=mysite/whatisashelter-easylang.html"> the designated protected area

Clone this wiki locally