Ricky Buchanan (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
jeshyr) wrote in ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_accessibility2011-10-31 07:47 pm
jeshyr) wrote in dw_accessibility2011-10-31 07:47 pm
New Accessibility Fixes on DW!
A bunch of new accessibility fixes have gone live on the Dreamwidth site with the latest code push! They're all listed in the dw_maintenance entries but they're mixed in with tons of other stuff so I'm pulling them out to list here for those people who are interested...
(Text is copied from the code tours describing these fixes)
Bug 3959: Wrap image alt attribute value with apostrophes
Category: Site Layout/Navigation
Patch by:skakri
Description: Back-end change to icons to help avoid breaking things.
Bug 3905: In-page text refers to "Reading List" instead of "Reading Page" at several points.
Category: Misc UI/Frontend
Patch by:rb
Description: In various places around the site, we were using the term "reading list" when we meant "reading page". In some cases, these could even be simplified further; "Add to your reading list" is better expressed as "Subscribe to ", for example. This patch fixes up all of these issues!
Bug 3927: add number of month to name of month on cc field
Category: Payments
Patch by:rb
Description: Springing out of a discussion in dw_accessibility, the expiration dates on credit cards are almost always printed using two digits each for the month and the year, but we were using month names in our credit card payment page, forcing people to have to convert the number on their card into a name. This patch modifies the list so that instead of "January", "February", and so on, the list displays "January - 01", "February - 02", and so on. (The name still comes first so that people can use the keyboard to type the first letter and go to the appropriate month.)
Bug 3905: In-page text refers to "Reading List" instead of "Reading Page" at several points.
Category: Misc UI/Frontend
Patch by:rb
Description: In various places around the site, we were using the term "reading list" when we meant "reading page". In some cases, these could even be simplified further; "Add to your reading list" is better expressed as "Subscribe to ", for example. This patch fixes up all of these issues!
Note: There have also been a bunch of other smaller "language clarifying" bugs but I don't have the energy to copy them all over here! They're not marked as "accessibility" in our bug tracker but I think clear and understandable language is totally an accessibility issue so I'm noting them here.
Bug 3298: Option to view top level comments only
Category: Journal contents
Suggested by:lightgetsin
Patch by:allen
Description: ...this bug, which utilises the aforementioned reply-hiding functionality to allow people to view just the top-level comments on any entry. This will show up as a link next to the one made for the ?view=flat mode above the comments (see two bugs up to bug 1474), and to view the replies to a comment you'll need to click the link on the comment to show the replies. This should prove quite handy for things like friending memes and such!
Bug 3416: Suspended entry link has 'here' as link text
Category: Misc UI/Frontend
Description: Slight fix in site copy on a suspended entry so that the text for a link isn't just an utterly and entirely not-descriptive, not helpful 'here'.
Bug 3870: Add alt attribute for locked icon on entries in style=light
Category: Misc UI/Frontend
Suggested by:faithofone
Patch by:rb
Description: The little lock icons in various places (including style=light pages) was missing alt text (which makes them audible for screen readers, visible for text-only users and people on very slow connections, and tool-tippy for the tool-tip-enabled). This patch inserts informative alt text on all little lock icons.
Bug 3912: style=mine not working on journal pages
Category: Style System
Patch by:exor674
Description: Unfortunately, somewhere in the code, “mine” got to be from the perspective of the journal being viewed, rather than the user setting the option “style=mine” in the URL.exor674 noticed this and fixed it.
(I patched several of these, which is totally exciting for me as I'm just a beginner at programming for Dreamwidth.)
This code push also activates the very first beta testing of our new Create Entries page! This is a complete rewrite of the old Update page in order to allow for future expansion and new features such as draft posts, scheduled posts, recurring posts, expanding the range of what can be posted to your journal, and a whole host of other awesome things. It's not finished yet - the biggest thing you'll notice missing is the rich text editor (RTE), you have to type posts in HTML if you're using this beta feature.
This you will only see this new beta update page if you turn on beta testing, and you can turn it off at any time. Check outdw_beta for more details about this.
I'd like to really encourage people who use accessibility technologies of any type, including screen readers, magnifying software, large text, speech-to-text software, keyboard-only access, etc., to try this beta out if you have some spare time and energy.fu, who is doing the programming for this new page, is very aware of accessibility needs and we all want to get it as accessible as possible so we need to know what's not easily accessible yet! Pop over to dw_beta and read the post about the new Create Entries page and leave your comments over there so we can keep improving.
Cheers,
rb
dw_maintenance entries but they're mixed in with tons of other stuff so I'm pulling them out to list here for those people who are interested...(Text is copied from the code tours describing these fixes)
Bug 3959: Wrap image alt attribute value with apostrophes
Category: Site Layout/Navigation
Patch by:
skakriDescription: Back-end change to icons to help avoid breaking things.
Bug 3905: In-page text refers to "Reading List" instead of "Reading Page" at several points.
Category: Misc UI/Frontend
Patch by:
rbDescription: In various places around the site, we were using the term "reading list" when we meant "reading page". In some cases, these could even be simplified further; "Add
Bug 3927: add number of month to name of month on cc field
Category: Payments
Patch by:
rbDescription: Springing out of a discussion in dw_accessibility, the expiration dates on credit cards are almost always printed using two digits each for the month and the year, but we were using month names in our credit card payment page, forcing people to have to convert the number on their card into a name. This patch modifies the list so that instead of "January", "February", and so on, the list displays "January - 01", "February - 02", and so on. (The name still comes first so that people can use the keyboard to type the first letter and go to the appropriate month.)
Bug 3905: In-page text refers to "Reading List" instead of "Reading Page" at several points.
Category: Misc UI/Frontend
Patch by:
rbDescription: In various places around the site, we were using the term "reading list" when we meant "reading page". In some cases, these could even be simplified further; "Add
Note: There have also been a bunch of other smaller "language clarifying" bugs but I don't have the energy to copy them all over here! They're not marked as "accessibility" in our bug tracker but I think clear and understandable language is totally an accessibility issue so I'm noting them here.
Bug 3298: Option to view top level comments only
Category: Journal contents
Suggested by:
lightgetsinPatch by:
allenDescription: ...this bug, which utilises the aforementioned reply-hiding functionality to allow people to view just the top-level comments on any entry. This will show up as a link next to the one made for the ?view=flat mode above the comments (see two bugs up to bug 1474), and to view the replies to a comment you'll need to click the link on the comment to show the replies. This should prove quite handy for things like friending memes and such!
Bug 3416: Suspended entry link has 'here' as link text
Category: Misc UI/Frontend
Description: Slight fix in site copy on a suspended entry so that the text for a link isn't just an utterly and entirely not-descriptive, not helpful 'here'.
Bug 3870: Add alt attribute for locked icon on entries in style=light
Category: Misc UI/Frontend
Suggested by:
faithofonePatch by:
rbDescription: The little lock icons in various places (including style=light pages) was missing alt text (which makes them audible for screen readers, visible for text-only users and people on very slow connections, and tool-tippy for the tool-tip-enabled). This patch inserts informative alt text on all little lock icons.
Bug 3912: style=mine not working on journal pages
Category: Style System
Patch by:
exor674Description: Unfortunately, somewhere in the code, “mine” got to be from the perspective of the journal being viewed, rather than the user setting the option “style=mine” in the URL.
exor674 noticed this and fixed it.(I patched several of these, which is totally exciting for me as I'm just a beginner at programming for Dreamwidth.)
This code push also activates the very first beta testing of our new Create Entries page! This is a complete rewrite of the old Update page in order to allow for future expansion and new features such as draft posts, scheduled posts, recurring posts, expanding the range of what can be posted to your journal, and a whole host of other awesome things. It's not finished yet - the biggest thing you'll notice missing is the rich text editor (RTE), you have to type posts in HTML if you're using this beta feature.
This you will only see this new beta update page if you turn on beta testing, and you can turn it off at any time. Check out
dw_beta for more details about this.I'd like to really encourage people who use accessibility technologies of any type, including screen readers, magnifying software, large text, speech-to-text software, keyboard-only access, etc., to try this beta out if you have some spare time and energy.
fu, who is doing the programming for this new page, is very aware of accessibility needs and we all want to get it as accessible as possible so we need to know what's not easily accessible yet! Pop over to dw_beta and read the post about the new Create Entries page and leave your comments over there so we can keep improving.Cheers,
rb
no subject
no subject
There are more than usual in this code push because I have been specifically picking off all the small accessibility bugs to do while I'm learning programming and I've done all the really easy ones now so the numbers will go down to normal again I suspect.
I'll try to keep doing this whenever there's a code push, it's cool to have a record.
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject