Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Oliver Foster
    @oliverfoster
    i'm free on tuesday next week if you want to have a call about it?
    GitJassal
    @GitJassal
    Next Tuesday works for me anytime after 11:00
    Oliver Foster
    @oliverfoster
    cool, shall we say 11 - 13am ?
    Hans Hillen
    @hhillen:matrix.org
    [m]
    Is there a reason for the way Adapt handles headings? (visually hidden div with heading role and aria-level, visible div with aria-hidden)
    Oliver Foster
    @oliverfoster
    so that we can add completion statuses to the heading for screen readers only
    Hans Hillen
    @hhillen:matrix.org
    [m]
    Why not just use regular headings and prepend or append visually hidden status text to those?
    Oliver Foster
    @oliverfoster
    it had more in it when it was originally written and it was simplified down to what we have now, it just happened like that
    Hans Hillen
    @hhillen:matrix.org
    [m]
    In config.json, what exactly does _accessibility._ariaLevels._componentItem (set to 5 by default) represent? Is it possible for a component to be broken up in smaller sections?
    Oliver Foster
    @oliverfoster
    Hot graphic / narrative / accordion item titles
    For example
    Which component would you like to be broken into smaller sections?
    Hans Hillen
    @hhillen:matrix.org
    [m]
    Thanks, that answers my question.
    I wasn't looking to break up a component myself, just wondering what componentItem meant.
    I'm trying to come up with a consistent approach for my script to generate a correct heading structure (without gaps in heading levels).
    With my approach, a component's heading level is determined by the presence of a displayTitle on its parent block and / or article. This means that component heading levels can range from 2 to 4. Now that I understand what componentItems are, I realize I'll also have to keep track of their level (i.e., 3 to 5).
    Hans Hillen
    @hhillen:matrix.org
    [m]
    On a side note, I just noticed that the accordion component doesn't actually use heading markup for its item titles, as recommended by the APG. Is this something I should log as an issue and / or submit as a PR?
    Oliver Foster
    @oliverfoster
    No there are, as always, a few ways to do everything accessible.
    h tag have an implied role=heading and aria-level=1/2/3/4/5/6/7 etc, we just use a div/span with explicitly defined role=heading and aria-level, it's easier for the framework.
    The effect is the same.
    Hans Hillen
    @hhillen:matrix.org
    [m]
    Got it, it turned out I was looking at an old version of the plugin
    RMurray89
    @RMurray89
    Hi just wanted to check the official stance on Adapt 5 accessibility on iOS? I know there is documentation around v4 stating the primary test environment is JAWS/ NVDA on desktop. Haven't seen similar documentation for V5. I have some feedback from testers who've had some difficulty. It's mainly around focus on things like modals (i.e. when you close the modal focus goes to the top of the page), same with video player in full-screen mode amongst others.
    Oliver Foster
    @oliverfoster
    It's mostly contingent on which fw/core version you're using and which device and how they're interacting with it.
    Testers and accessibility outcomes vary wildly. Most testers I've met have very little understanding of how to use accessible technology. It would be helpful if you could clarify.
    did you try https://github.com/cgkineo/adapt-csvToTable for accessible tables?
    RMurray89
    @RMurray89
    Hi Oliver, I'll have a look and see if I can share some of the testers feedback. The link you shared above gives a 404 :(
    Oliver Foster
    @oliverfoster
    Try again
    RMurray89
    @RMurray89
    Thanks Oliver I managed to download that. Will have a proper look at it a little later. Is it possible to use it in the authoring tool? I did manage to install it. Just not sure how to provide csv data?
    Has anyone noticed the js-heading with aria-level not being outputted? I've found on one component title, it has no js-heading so no heading level for screen readers. Accessibility state is enabled..
    image.png
    Oliver Foster
    @oliverfoster
    There's examples in the readme
    Is that a text component?
    RMurray89
    @RMurray89
    @oliverfoster yeah that's a text component. It should have an aria level 3.
    Oliver Foster
    @oliverfoster
    it's clearly missing the heading div
    either the component is messed up or configured incorrectly
    _disableAccessibilityState directly controls the production of that div
    RMurray89
    @RMurray89
    I'll try deleting and readding the block and let you know if that fixes it..
    Oliver Foster
    @oliverfoster
    Why not debug it?
    RMurray89
    @RMurray89
    Yeah I'm a designer and while I can work with html/ css/ less and understand aria/ wcag I'm not too clued up on the JS/ programming side of things! Can read JS and know the basics. If you can give me some pointers I can see if I can debug it..
    Oliver Foster
    @oliverfoster
    mac or windows?
    RMurray89
    @RMurray89
    Windows
    Oliver Foster
    @oliverfoster
    Chrome / Firefox / Edge or Internet Explorer?
    RMurray89
    @RMurray89
    Chrome
    Rich Knop
    @RichKnop
    How do you all work with Long Descriptions for complex images in ADAPT. If you have alt text over 250 characters, is there any extensions that allows long descriptions or is there something that can be done within the default graphic component?
    I was looking into creating a new graphic component that has the transcript functionality from the media component that can be utilize for long descriptions.
    Oliver Foster
    @oliverfoster
    We have an outstanding pull request for long descriptions
    It needs testing and a few amends
    Oliver Foster
    @oliverfoster
    It now just needs testing
    Rich Knop
    @RichKnop

    Is there any reason to not have the Accessibility enable checkbox under the course configuration checked? What all does this trigger? Is there any documentation on this anywhere to review?

    I was doing some 508 testing on two courses where one, the narrative worked properly and one did not with NVDA. After searching around, I realized the check box was not checked. After checking the checkbox, NVDA read correctly and moved focus after the next button was selected to move to the next slide.

    I am just checking if there are any cases where you might not want it checked, where any course we produce is fully reviewed for 508 compliance.

    Oliver Foster
    @oliverfoster
    No, turn it on and leave it on. We used to have a totally different accessibility mode that you had to turn on, that's a left over reminant that really isn't necessary to turn off.
    It basically now controls focus management.