276 Matching Annotations
  1. Oct 2018
    1. Finding the Place Where Accessibility and SEO Happily Co-Exist Carie Fisher
      • SEO = strategic changes to websites to increase search engine ranking
      • A11y = designing & building websites so anyone can interact regardless of ability.
      • Structure: good for search engine bots AND assistive tech users. Using semantic HTML, clear & consistent architecture improve scan-ability for bots and humans alike. (Tip: don’t overuse h1 tags. Search engines will down-rank you if you have too many)
      • Links & media: a11y also helps users with low bandwidth & those who view content without sound (i.e., when in public). Descriptive link text, alt text, consistent file naming, all help with SEO as well as a11y.
      • Content: include bullets, lists, & white space (preferred by SE bots and people with attention/cognitive disorders) and aim for 9th-grade reading level for copy
      • A11y Style Guide available here
    2. Assistive technology: training, UX and design: what devs need to know about UX and Aging Sassy Outwater
      • AT is a barrier for seniors accessing technology because it’s expensive & there’s a learning curve
      • biggest issues = overestimating what AT can do or underestimating what seniors can do.
      • important to understand the emotional component of seniors needing assistive tech. For some it’s traumatic to acquire disability so they are coming to your product already frustrated.
      • What makes a good website for an elderly end user? Obvious items include text size, mouse and keyboard use both accounted for, basically WCAG standards
      • Seniors like what works, meaning they hate upgrading / updating their tech.
      • “Don’t make me hunt down my mouse cursor in a mass of text”
      • Consider cognitive load and distractions. Moving elements or pop ups break focus and cause the user to forget what they were doing.
      • Use clear error message so when a form can’t be submitted the user knows where the error is and how to fix it
      • Personas should consider: various short term memory lengths, lack of tech knowledge, and the perspectives of real people with disabilities
    3. Steve Faulkner
      • ARIA should be used sparingly— “the first rule of ARIA is only use it when you need to”
      • when AJAX first started being used JAWS and other screen readers didn’t look for updates after page load, so pages built with AJAX presented a problem
      • the idea that screen readers are to blame when they don’t work with HTML5 is a myth. Remember that many new HTML5 standards not yet implemented for browsers.
      • Steve has created a github repo so people can file issues for bugs with JAWS / VFO
  2. Aug 2018
    1. Wheelmap.org is an online map for wheelchair accessible places. Everyone can easily find, register and change places on the website or via an iPhone - as with Wikipedia. The platform went online in September 2010. Already after half a year, volunteers have registered over 40,000 places, every day 100 new places are added. Since November 2010, there is also the free iPhone app.A simple traffic light system marks the wheelchair accessibility of the places: Green means unrestricted access. For example, orange marked places do not have a toilet. Locations that are displayed in red can not be entered by wheelchair users. With the help of this traffic light, people with reduced mobility can find suitable places in their environment and even worldwide. Since places are also listed that are not wheelchair accessible, owners of cafés or other public places are made aware of the problem and encouraged to think about wheelchair accessibility in their rooms.

      WheelMap - For Wheelchair Accessible Places

    1. Little project that aims at raising awareness for accessibility in public transport systems. It uses a simple slider to visualize how the public transport system looks like if all the non-accessible stations are erased. There is an elaborate how-to available, suitable for non-coders on the projects github site.

      ACCESS MAP - Accessibility in Public Transport Systems

    1. Accessibility of Content

      Annotations offer exciting opportunities in the area of accessibility.

  3. Jul 2018
    1. Following inclusive design, we look to make interventions not only to support accessibility for specific types of users, but to make annotation a better and easier experience for everyone.

      These interventions include complying with Level AA Success Criteria set out by the W3C in the Web Content Accessibility Guidelines (WCAG) 2.0.

  4. Jun 2018
    1. Regardless of conformance, it is vital for accessibility that there be good contrast for text and that links be discernible.

      test

  5. May 2018
  6. Apr 2018
    1. Interview with Dr. Richards

      Interesting idea to incorporate the interview content in three ways. Those who want to use it as an article can do so, and those who want the original source can still access it.

  7. Mar 2018
    1. Shockingly, the language of “disciplinary landscapes” and “infrastructure” and “free-floating signifiers” does not set the average undergraduate’s pulse a-twittering. Indeed, to assign such a piece to a class of undergraduates is to forget our audience entirely.

      It may be wise for a DH scholar to write an article geared towards undergraduates. Similar to the way this article is written, perhaps the use of memes and "slang" could create a more accessible (and interesting) way for undergraduates to understand digital humanities.

    1. avoid digital redlining,[26] creating inequities (however unintentionally) through the use of technology.

      So many challenges here, and we really must address all of them. I'm also interested in learning how to make sure my websites and other affordances I use are accessible to people with disabilities.

  8. Feb 2018
    1. They now stand out as the only one in the class (or, if they’re lucky, one of two) who gets to use a device while other students wonder just why they get to use one. I have seen a couple of students on social media say that as soon as they see a “no devices” policy on a syllabus they drop the class because of this concern.

      Good rationale for not enacting a blanket classroom tech ban

    1. Beyond compliance, this effort is a key component of valuing diversity in an educational ecosystem that supports inclusivity and universal design in education.

      accessibility over compliance. Love it.

  9. Jan 2018
    1. there should be some way for a blind screen reader user to know exactly which text is being discussed.
    2. there should be notification of the number of highlights of different types, a way to navigate to each highlight and to choose which type of (color) highlight to navigate between
    3. Keyboard access to any notes available at the highlight location is necessary

      Note: this should be independent of screen reader function. People who are sighted but have mobility difficulties need to be able to make and access highlights using their keyboard.

    4. a standard should be provided for categorizing highlights semantically.

      This is something we could work on and contribute back to the W3C community

    5. users of smaller screens

      not always considered in matters of accessibility, but important

    6. can closely mirror highlighting with a highlighter pen in a printed book

      Can, but doesn't have to - in fact online highlighting can be EASIER for people with certain disabilities

    1. A 4.5:1 contrast between the non-link text color and the background. A 4.5:1 contrast between the link text color and the background. A 3:1 contrast between the link text color and the surrounding non-link text color.
  10. Dec 2017
  11. Nov 2017
    1. In order to assess and document the level of compliance, completion of this information by an authorized representative of the supplier organization will provide the University of Colorado Procurement Service Center, and the campus affiliates it serves, with knowledge regarding the level of compliance and satisfaction of this policy and related standards with respect to the offered products and services.
    1. If OER is appealing because they can help make knowledge more accessible, then we must care about the myriad issues -- from child care to transportation -- that prevent our potential students from even coming to our classrooms in the first place.

      Broader concept of access to education.

  12. Sep 2017
    1. We’re working on that. The next supported browser is likely to be Firefox.

      Is there an appetite for an app perhaps? EndNote has one, and I use t a lot as part of my digital workflow as I move from phone to tablet, and sometimes desktop. It seems to me that to tether us to a desktop (even if it is a laptop) is becoming somewhat anachronistic these days.

      I'm also curious about how accessible hypothes.is is. Can you comment on that? I mean from a WCAG perspective.

  13. Aug 2017
  14. Jul 2017
    1. Bringing User Experience to Education: UDL and Inclusion for the 21st Century" and my keynote address, which I refer to at the conclusion of the post, is about "Universal Learning Experiences: How UDL and UX Structure Inclusion & Transfer in Education for All." 

      @kgoin Conference

  15. Jun 2017
  16. May 2017
    1. For example, with WAI-ARIA, developers can identify regions of pages and enable keyboard users to easily move among regions, rather than having to press Tab many times.
    2. For example, if the content of a Web page changes in response to user actions or time- or event-based updates, that new content may not be available to some people, such as people who are blind or people with cognitive disabilities who use a screen reader.
  17. Apr 2017
    1. 1. Navigate to the NVDA menu NVDA+N2. Down arrow to preferences, and press right arrow.3. Down arrow to document settings, and press enter.4. Tab through the dialog box. One of the options is report clickable.5. Uncheck that box, and press enter.
    1. Navigating by ARIA Landmarks with Screen Readers In JAWS, use the semi-colon key to jump to the next landmark, or use shift + semi-colon to go backward through landmarks. In NVDA, use the D key to jump to the next landmark, or use shift + D to go backward through landmarks. In VoiceOver, use CTRL + ALT + U to start the web rotor, then, if necessary, use the left or right arrow keys to display the list of landmarks (the rotor also displays lists of headings, links, and web spots), then use the down arrow key to navigate through the list of landmarks.
  18. Mar 2017
  19. Feb 2017
    1. What emerged was a prototype for a feature that could let blind or visually impaired people put their fingers over an image and have their phones read them a description of what’s happening.

      This is super cool!

    1. 1 am aware it will be said, that written lan-guage is only a copy of that which is spoken, and has a constant reference to articulation; the char-aclers upon paper, being only symbols of articu-late sounds

      I know we're not supposed to say "I disagree," so I'll try to go about this a bit more cautiously. This line of thinking is, I think, one of the more pervasive misconceptions about composition still today. When considering accessibility options, a lot of people with disabilities are often told, "Just get some dictation software." But this very rarely does what people need it to do, not just because of the editing difficulty, but because the ways we talk (and listen) are often just too different than the ways we write (and read).

  20. Jan 2017
    1. Those of us who traffic in this word, "rhetoric," have a great deal of experience with the ubiquity of the question "What is rhetoric?" and the countless idioms and situations in which it reappears.

      Perhaps Muckelbauer's dilemma here is rooted in the fact he is a bad rhetorician.

      The inability to craft an accessible definition or understanding of rhetoric for those who are not engaged with field is, in my opinion, bad rhetoric. Can rhetoric be justified if rhetoricians are unable to craft effective rhetoric to explain it?

    2. We don't necessarily do an injustice to the diffuse history and conceptual promiscuity of the term by giving a single answer.

      While offering a single answer to this question may appearing limiting, a basic study of rhetoric will tell you that the single answer is necessary as that is the rhetorical form that is demanded.

    1. Thank you for your query. I'm afraid that while improving the accessibility (particularly keyboard navigability) of Hypothesis is high on our list of priorities, it's still a little rough in places, and we don't have an accessibility report at the moment.

      I'm commenting here because the ticket is closed (and consequently locked), but we do have an accessibility report from August 2016 focused only on the client at https://docs.google.com/document/d/1aV4yOqR-rbBjy0t4z3cbmDfz4zKmJMt_YEXjYthGODQ/edit?ts=5745a68c

  21. Jul 2016
  22. Mar 2016
    1. universally inclusive and accessible

      On the one hand, of course. On the other...default accessibility it both difficult and can cut down on the type of "fun" and or "engaging" applications you might use.

  23. Dec 2015
    1. The EDUPUB Initiative VitalSource regularly collaborates with independent consultants and industry experts including the National Federation of the Blind (NFB), American Foundation for the Blind (AFB), Tech For All, JISC, Alternative Media Access Center (AMAC), and others. With the help of these experts, VitalSource strives to ensure its platform conforms to applicable accessibility standards including Section 508 of the Rehabilitation Act and the Accessibility Guidelines established by the Worldwide Web Consortium known as WCAG 2.0. The state of the platform's conformance with Section 508 at any point in time is made available through publication of Voluntary Product Accessibility Templates (VPATs).  VitalSource continues to support industry standards for accessibility by conducting conformance testing on all Bookshelf platforms – offline on Windows and Macs; online on Windows and Macs using standard browsers (e.g., Internet Explorer, Mozilla Firefox, Safari); and on mobile devices for iOS and Android. All Bookshelf platforms are evaluated using industry-leading screen reading programs available for the platform including JAWS and NVDA for Windows, VoiceOver for Mac and iOS, and TalkBack for Android. To ensure a comprehensive reading experience, all Bookshelf platforms have been evaluated using EPUB® and enhanced PDF books.

      Could see a lot of potential for Open Standards, including annotations. What’s not so clear is how they can manage to produce such ePub while maintaining their DRM-focused practice. Heard about LCP (Lightweight Content Protection). But have yet to get a fully-accessible ePub which is also DRMed in such a way.

  24. Nov 2015
  25. Sep 2015
    1. So to sum up: It should be an active design choice whether you want to enable users to change the font size independently to parts of or all layout and graphics. If so, pixels will probably not be your friend. If not, I’d say it’s mainly a matter of personal taste and/or project.

      This is good guidance on when/whether to use em vs. px sizing

    2. Useful article giving an overview of the history of how browser zooming affected CSS units.

      Makes a strong overall recommendation to use px almost everywhere, except where component size elements should specifically relate to their font.

    3. In version 7 of internet explorer that was released in October 2006 there was a very prominent zoom icon on the bottom right of the browser window. And guess what… The zoom function was just modifying the CSS reference pixel in the browsers CSS rendering engine!

      This is a useful resource on the history of zooming and accessibility in browsers.

      See also this argument

    1. This is not true nowadays. Pressing Ctrl+ and Ctrl- in any modern browser will scale the pixel values as well. It has been like this for a while now.
  26. Aug 2015
    1. Setting the tabindex of the focused element to "0" ensures that if the user tabs away from the widget and then returns, the selected item within the group retains focus. Note that updating the tabindex to "0" requires also updating the previously selected item to tabindex="-1". This technique involves programmatically moving focus in response to key events and updating the tabindex to reflect the currently focused item. To do this:

      This looks like a lot of manual work for web authors that many are likely to get wrong. How much of this could be automated?

  27. May 2015
    1. descriptively captioned video stills

      There's a relationship here between the method & accessibility practices, right?

  28. Feb 2015
    1. For mobile we can’t use the desktop adder since Android and iOS present their own popup menus.

      Sites like Medium do as well. We may wish to consider that.

    2. This would be good for accessibility as screen readers won’t have to navigate the dom looking for the button.

      Nice point.