![]() ![]() I worked on a major public financial site with my last company and one time we had a link that was not as descriptive as it should have been. These days making websites accessible is a necessity, not just for government but for everybody. We had to remove the better implementation in favor of the prescriptive one. I'd inserted invisible links and other tricks to make the site work well with a screen reader, but these weren't the "normal" pattern so the site failed the accessibility test. This would check for labels and such to make sure the content followed the published standards for how to implement accessibility. Their standard for testing accessibility was using an online scanning tool. I used the computer through JAWS and updated our application until I could use it seamlessly without the monitor turned on. I wanted to do it right and really understand how the application would be used with assistive technology, so I asked for a copy of JAWS and they bought it even thought it was pretty expensive. ![]() This was my first exposure to building accessible websites. Being government though, their implementation of them was not exactly thought out. As a government website their accessibility requirements were ahead of where commercial sites were at the time. Mouseless at NASAĪround 2001 I worked briefly as a contractor at NASA, through B-Line Express. If I wasn't seeing what was on the screen, I wouldn't have even known the modal was there. I wasn't able to get the focus onto the button on the modal and tabbing around continued to tab through the elements in the shaded background behind the modal. I'm not even sure what I clicked on to show the modal, but once it was up, it couldn't go away. It got worse still when a modal popped up on the screen. This should be true for all users, not just when using keyboard navigation. When a user clicks sign-in to go to the sign-in page, they want to sign-in. To go from clicking on "Sign-in" on the previous page to actually focusing on the email textbox, I had to hit tab 131 times (yes, I counted). The sign-in page didn't have a skip link and as I tabbed through the menu, it tabbed through not only the main menu of five items but also every item in the (invisible) submenus. I navigated to the sign-in link ok and hit enter to go to that page. Things got worse when I tried to sign-in. When a modal shows, such as the "my drafts" list, tabbing through the document correctly only tabs through the links on the modal. One really nice thing that LinkedIn did right is how they handled modals (pop-ups). I never found a list of other shortcuts for things like changing the paragraph style or creating a link. I wasn't sure it was keeping the context of which text previously had focus, but it did.įunny thing, when I tried to search for keyboard shortcuts for LinkedIn, the top search results are all LinkedIn Learning courses on using keyboard shortcuts in other apps. Styling headings and quotes was attainable, although with a lot of tabbing. Common shortcuts for bold, italics, and underline all worked. Authoring worked well I was able to navigate to the relevant parts in an article, upload and position images. The "Skip to search"and "Skip to main content" buttons also behaved exactly as advertised. Who is the post from? What company are they with? ![]() These links are just titles though lacking important context for the LinkedIn feed. The jump jump list has links for groups and hashtags first, then links for individual posts within the feed. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |