#inaccessibility — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #inaccessibility, aggregated by home.social.
-
Wow, #Inaccessibility strikes again. I booked a ride for a friend with #Uber. It was canceled. It wasimpossible to dispute my case with #iOS because the buttons weren't labeled, and the same was true for #Android, but thanks to the describe screen feature I could make it work.
-
Wow, #Inaccessibility strikes again. I booked a ride for a friend with #Uber. It was canceled. It wasimpossible to dispute my case with #iOS because the buttons weren't labeled, and the same was true for #Android, but thanks to the describe screen feature I could make it work.
-
Wow, #Inaccessibility strikes again. I booked a ride for a friend with #Uber. It was canceled. It wasimpossible to dispute my case with #iOS because the buttons weren't labeled, and the same was true for #Android, but thanks to the describe screen feature I could make it work.
-
Wow, #Inaccessibility strikes again. I booked a ride for a friend with #Uber. It was canceled. It wasimpossible to dispute my case with #iOS because the buttons weren't labeled, and the same was true for #Android, but thanks to the describe screen feature I could make it work.
-
Well, it's convoluted as all hell, but you technically can send a message if you're willing to take quite a few steps. If you turn on screen recognition, the microphone button appears at the bottom right, as it always did. Then, you can flick to the message thing and double tap. The keyboard pops up. Type your message, scrub to hide keyboard, and with screen recognition again, the send is at the bottom right. Or, you can just avoid telegram and use something simpler. #Telegram #iOS #Inaccessibility
-
Well, it's convoluted as all hell, but you technically can send a message if you're willing to take quite a few steps. If you turn on screen recognition, the microphone button appears at the bottom right, as it always did. Then, you can flick to the message thing and double tap. The keyboard pops up. Type your message, scrub to hide keyboard, and with screen recognition again, the send is at the bottom right. Or, you can just avoid telegram and use something simpler. #Telegram #iOS #Inaccessibility
-
Well, it's convoluted as all hell, but you technically can send a message if you're willing to take quite a few steps. If you turn on screen recognition, the microphone button appears at the bottom right, as it always did. Then, you can flick to the message thing and double tap. The keyboard pops up. Type your message, scrub to hide keyboard, and with screen recognition again, the send is at the bottom right. Or, you can just avoid telegram and use something simpler. #Telegram #iOS #Inaccessibility
-
Well, it's convoluted as all hell, but you technically can send a message if you're willing to take quite a few steps. If you turn on screen recognition, the microphone button appears at the bottom right, as it always did. Then, you can flick to the message thing and double tap. The keyboard pops up. Type your message, scrub to hide keyboard, and with screen recognition again, the send is at the bottom right. Or, you can just avoid telegram and use something simpler. #Telegram #iOS #Inaccessibility
-
🚫404 Error: Journalism Not Found🚫. In a stunning display of cutting-edge #technology, this article offers a mind-bending glimpse into... absolutely nothing. 😅 Apparently, the secret to understanding complex geopolitical issues is to make them completely inaccessible. 🤖🔒👀
https://www.thecairoreview.com/essays/gaza-israels-ai-human-laboratory/ #404Error #JournalismNotFound #Geopolitics #Satire #Inaccessibility #HackerNews #ngated -
🚫404 Error: Journalism Not Found🚫. In a stunning display of cutting-edge #technology, this article offers a mind-bending glimpse into... absolutely nothing. 😅 Apparently, the secret to understanding complex geopolitical issues is to make them completely inaccessible. 🤖🔒👀
https://www.thecairoreview.com/essays/gaza-israels-ai-human-laboratory/ #404Error #JournalismNotFound #Geopolitics #Satire #Inaccessibility #HackerNews #ngated -
🚫404 Error: Journalism Not Found🚫. In a stunning display of cutting-edge #technology, this article offers a mind-bending glimpse into... absolutely nothing. 😅 Apparently, the secret to understanding complex geopolitical issues is to make them completely inaccessible. 🤖🔒👀
https://www.thecairoreview.com/essays/gaza-israels-ai-human-laboratory/ #404Error #JournalismNotFound #Geopolitics #Satire #Inaccessibility #HackerNews #ngated -
🚫404 Error: Journalism Not Found🚫. In a stunning display of cutting-edge #technology, this article offers a mind-bending glimpse into... absolutely nothing. 😅 Apparently, the secret to understanding complex geopolitical issues is to make them completely inaccessible. 🤖🔒👀
https://www.thecairoreview.com/essays/gaza-israels-ai-human-laboratory/ #404Error #JournalismNotFound #Geopolitics #Satire #Inaccessibility #HackerNews #ngated -
🚫404 Error: Journalism Not Found🚫. In a stunning display of cutting-edge #technology, this article offers a mind-bending glimpse into... absolutely nothing. 😅 Apparently, the secret to understanding complex geopolitical issues is to make them completely inaccessible. 🤖🔒👀
https://www.thecairoreview.com/essays/gaza-israels-ai-human-laboratory/ #404Error #JournalismNotFound #Geopolitics #Satire #Inaccessibility #HackerNews #ngated -
Sheri Byrne-Haber’s Blog: Accessibility Triumph Thursday: BrokenLifts.org. “BrokenLifts is a grassroots initiative providing real-time information about out-of-service elevators in Berlin’s public transportation system. For wheelchair users and others who depend on elevators, this resource saves people from wasted trips and gives them back some control over their commutes. It’s a shining […]
-
Sheri Byrne-Haber’s Blog: Accessibility Triumph Thursday: BrokenLifts.org. “BrokenLifts is a grassroots initiative providing real-time information about out-of-service elevators in Berlin’s public transportation system. For wheelchair users and others who depend on elevators, this resource saves people from wasted trips and gives them back some control over their commutes. It’s a shining […]
-
"Tackling #Ableism, #Inaccessibility and #Discrimination should be a priority for the entire #Music industry”: The startling systemic issues facing #Disabled #Musicians highlighted in new report.
-
"Tackling #Ableism, #Inaccessibility and #Discrimination should be a priority for the entire #Music industry”: The startling systemic issues facing #Disabled #Musicians highlighted in new report.
-
"Tackling #Ableism, #Inaccessibility and #Discrimination should be a priority for the entire #Music industry”: The startling systemic issues facing #Disabled #Musicians highlighted in new report.
-
Just searched the Uber > Riders website.
No returns for "blind" or "vision impaired".
This is reasonable adjustment?
I don't think so.
-
Just searched the Uber > Riders website.
No returns for "blind" or "vision impaired".
This is reasonable adjustment?
I don't think so.
-
Just searched the Uber > Riders website.
No returns for "blind" or "vision impaired".
This is reasonable adjustment?
I don't think so.
-
Just searched the Uber > Riders website.
No returns for "blind" or "vision impaired".
This is reasonable adjustment?
I don't think so.
-
Just searched the Uber > Riders website.
No returns for "blind" or "vision impaired".
This is reasonable adjustment?
I don't think so.
-
#Disabled comedians speak out on career barriers due to widespread industry https://bit.ly/4c2AG4n
#inaccessibility #InclusionMatters #disability #DisabledAndCapable #inclusion -
#Disabled comedians speak out on career barriers due to widespread industry https://bit.ly/4c2AG4n
#inaccessibility #InclusionMatters #disability #DisabledAndCapable #inclusion -
#Disabled comedians speak out on career barriers due to widespread industry https://bit.ly/4c2AG4n
#inaccessibility #InclusionMatters #disability #DisabledAndCapable #inclusion -
#Disabled comedians speak out on career barriers due to widespread industry https://bit.ly/4c2AG4n
#inaccessibility #InclusionMatters #disability #DisabledAndCapable #inclusion -
#Disabled comedians speak out on career barriers due to widespread industry https://bit.ly/4c2AG4n
#inaccessibility #InclusionMatters #disability #DisabledAndCapable #inclusion -
#Disabled comedians speak out on career barriers due to widespread industry https://bit.ly/4c2AG4n
#inaccessibility #InclusionMatters #disability #DisabledAndCapable #inclusion -
#Disabled comedians speak out on career barriers due to widespread industry https://bit.ly/4c2AG4n
#inaccessibility #InclusionMatters #disability #DisabledAndCapable #inclusion -
#Disabled comedians speak out on career barriers due to widespread industry https://bit.ly/4c2AG4n
#inaccessibility #InclusionMatters #disability #DisabledAndCapable #inclusion -
Wellp, its a good thing I'm resourceful, persistent, and know a few things about code. I should not have had to go this far, and I should not have to do what I have to do in order to use my $1,400 network switch. Explnation follows.
But this is what ablism, lack of accessibility, lack of inclusive design, and lack of critical and forward thinking and planning by Netgear UX/UI designers, along with everyone else who does/makes these kinds of things/decisions causes for those who do not fall into their narrow mindset, views, and ideas of what is functional and useful design.
So it turns out that practically the entire web UI is Java script. Surprised, anyone?
On the VLAN membership page, there are ports and link aggregation group designations in a table, but of course not formatted at all like a proper table. Not yet surprised?
That's all well and good. But here's where it gets completely ablist, inaccessible and inconsiderate. The settings that control the port/LAG state is entirely images, and java-based clickable controls that don't actually respond to screen reader clickable identification/listing mechanisms. So if a port/LAG is part, not part, tagged, or untagged in a VLAN is only communicated as a visual signal in an image. And as we've seen in my previous post, even AI can't figure it out accurately more than half the time. Making adjustments to these controls is purely a guessing game.However, here's where my persistence, resourcefulness, and understanding of code comes in.
After slamming things around for a few hours, including my keyboard, I got the bright idea to start looking through the dev tools as well as page source.
It was then that I got frustrated once again, until I figured out that the VLAN membership stuff was in a separate iframe. So I had to look at its separate source specifically.
Once I found the code I needed, I then discovered that I could figure out what state each port/LAG was in by interpreting the html/java image code/tags and image names for each port. Two examples follow.
The first port is 10, and is removed from the VLAN. The second port is 11, and it is untagged in the VLAN.
<div class='portMember margin'><span class='portword'>10</span><div class='panels'><div class='portImage remImg'></div></div></div>
<div class='portMember margin'><span class='portword'>11</span><div class='panels'><div class='portImage untImg'></div></div></div>
So in the two above examples, we can see that the portword class is 10 and 11 respectively. This tells us what port we're dealing with.
Then later in the code, we can see that the portImage is either remImg or untImg. I've deduced that rem means remove, and unt means untagged.
So this is how I have to do VLANs in my $1,400 switch.
#Inaccessibility #Nonusability #Noninclusive #BadUX #BadUI #Ablism #RealEffects -
Wellp, its a good thing I'm resourceful, persistent, and know a few things about code. I should not have had to go this far, and I should not have to do what I have to do in order to use my $1,400 network switch. Explnation follows.
But this is what ablism, lack of accessibility, lack of inclusive design, and lack of critical and forward thinking and planning by Netgear UX/UI designers, along with everyone else who does/makes these kinds of things/decisions causes for those who do not fall into their narrow mindset, views, and ideas of what is functional and useful design.
So it turns out that practically the entire web UI is Java script. Surprised, anyone?
On the VLAN membership page, there are ports and link aggregation group designations in a table, but of course not formatted at all like a proper table. Not yet surprised?
That's all well and good. But here's where it gets completely ablist, inaccessible and inconsiderate. The settings that control the port/LAG state is entirely images, and java-based clickable controls that don't actually respond to screen reader clickable identification/listing mechanisms. So if a port/LAG is part, not part, tagged, or untagged in a VLAN is only communicated as a visual signal in an image. And as we've seen in my previous post, even AI can't figure it out accurately more than half the time. Making adjustments to these controls is purely a guessing game.However, here's where my persistence, resourcefulness, and understanding of code comes in.
After slamming things around for a few hours, including my keyboard, I got the bright idea to start looking through the dev tools as well as page source.
It was then that I got frustrated once again, until I figured out that the VLAN membership stuff was in a separate iframe. So I had to look at its separate source specifically.
Once I found the code I needed, I then discovered that I could figure out what state each port/LAG was in by interpreting the html/java image code/tags and image names for each port. Two examples follow.
The first port is 10, and is removed from the VLAN. The second port is 11, and it is untagged in the VLAN.
<div class='portMember margin'><span class='portword'>10</span><div class='panels'><div class='portImage remImg'></div></div></div>
<div class='portMember margin'><span class='portword'>11</span><div class='panels'><div class='portImage untImg'></div></div></div>
So in the two above examples, we can see that the portword class is 10 and 11 respectively. This tells us what port we're dealing with.
Then later in the code, we can see that the portImage is either remImg or untImg. I've deduced that rem means remove, and unt means untagged.
So this is how I have to do VLANs in my $1,400 switch.
#Inaccessibility #Nonusability #Noninclusive #BadUX #BadUI #Ablism #RealEffects -
Wellp, its a good thing I'm resourceful, persistent, and know a few things about code. I should not have had to go this far, and I should not have to do what I have to do in order to use my $1,400 network switch. Explnation follows.
But this is what ablism, lack of accessibility, lack of inclusive design, and lack of critical and forward thinking and planning by Netgear UX/UI designers, along with everyone else who does/makes these kinds of things/decisions causes for those who do not fall into their narrow mindset, views, and ideas of what is functional and useful design.
So it turns out that practically the entire web UI is Java script. Surprised, anyone?
On the VLAN membership page, there are ports and link aggregation group designations in a table, but of course not formatted at all like a proper table. Not yet surprised?
That's all well and good. But here's where it gets completely ablist, inaccessible and inconsiderate. The settings that control the port/LAG state is entirely images, and java-based clickable controls that don't actually respond to screen reader clickable identification/listing mechanisms. So if a port/LAG is part, not part, tagged, or untagged in a VLAN is only communicated as a visual signal in an image. And as we've seen in my previous post, even AI can't figure it out accurately more than half the time. Making adjustments to these controls is purely a guessing game.However, here's where my persistence, resourcefulness, and understanding of code comes in.
After slamming things around for a few hours, including my keyboard, I got the bright idea to start looking through the dev tools as well as page source.
It was then that I got frustrated once again, until I figured out that the VLAN membership stuff was in a separate iframe. So I had to look at its separate source specifically.
Once I found the code I needed, I then discovered that I could figure out what state each port/LAG was in by interpreting the html/java image code/tags and image names for each port. Two examples follow.
The first port is 10, and is removed from the VLAN. The second port is 11, and it is untagged in the VLAN.
<div class='portMember margin'><span class='portword'>10</span><div class='panels'><div class='portImage remImg'></div></div></div>
<div class='portMember margin'><span class='portword'>11</span><div class='panels'><div class='portImage untImg'></div></div></div>
So in the two above examples, we can see that the portword class is 10 and 11 respectively. This tells us what port we're dealing with.
Then later in the code, we can see that the portImage is either remImg or untImg. I've deduced that rem means remove, and unt means untagged.
So this is how I have to do VLANs in my $1,400 switch.
#Inaccessibility #Nonusability #Noninclusive #BadUX #BadUI #Ablism #RealEffects -
Wellp, its a good thing I'm resourceful, persistent, and know a few things about code. I should not have had to go this far, and I should not have to do what I have to do in order to use my $1,400 network switch. Explnation follows.
But this is what ablism, lack of accessibility, lack of inclusive design, and lack of critical and forward thinking and planning by Netgear UX/UI designers, along with everyone else who does/makes these kinds of things/decisions causes for those who do not fall into their narrow mindset, views, and ideas of what is functional and useful design.
So it turns out that practically the entire web UI is Java script. Surprised, anyone?
On the VLAN membership page, there are ports and link aggregation group designations in a table, but of course not formatted at all like a proper table. Not yet surprised?
That's all well and good. But here's where it gets completely ablist, inaccessible and inconsiderate. The settings that control the port/LAG state is entirely images, and java-based clickable controls that don't actually respond to screen reader clickable identification/listing mechanisms. So if a port/LAG is part, not part, tagged, or untagged in a VLAN is only communicated as a visual signal in an image. And as we've seen in my previous post, even AI can't figure it out accurately more than half the time. Making adjustments to these controls is purely a guessing game.However, here's where my persistence, resourcefulness, and understanding of code comes in.
After slamming things around for a few hours, including my keyboard, I got the bright idea to start looking through the dev tools as well as page source.
It was then that I got frustrated once again, until I figured out that the VLAN membership stuff was in a separate iframe. So I had to look at its separate source specifically.
Once I found the code I needed, I then discovered that I could figure out what state each port/LAG was in by interpreting the html/java image code/tags and image names for each port. Two examples follow.
The first port is 10, and is removed from the VLAN. The second port is 11, and it is untagged in the VLAN.
<div class='portMember margin'><span class='portword'>10</span><div class='panels'><div class='portImage remImg'></div></div></div>
<div class='portMember margin'><span class='portword'>11</span><div class='panels'><div class='portImage untImg'></div></div></div>
So in the two above examples, we can see that the portword class is 10 and 11 respectively. This tells us what port we're dealing with.
Then later in the code, we can see that the portImage is either remImg or untImg. I've deduced that rem means remove, and unt means untagged.
So this is how I have to do VLANs in my $1,400 switch.
#Inaccessibility #Nonusability #Noninclusive #BadUX #BadUI #Ablism #RealEffects -
Wellp, its a good thing I'm resourceful, persistent, and know a few things about code. I should not have had to go this far, and I should not have to do what I have to do in order to use my $1,400 network switch. Explnation follows.
But this is what ablism, lack of accessibility, lack of inclusive design, and lack of critical and forward thinking and planning by Netgear UX/UI designers, along with everyone else who does/makes these kinds of things/decisions causes for those who do not fall into their narrow mindset, views, and ideas of what is functional and useful design.
So it turns out that practically the entire web UI is Java script. Surprised, anyone?
On the VLAN membership page, there are ports and link aggregation group designations in a table, but of course not formatted at all like a proper table. Not yet surprised?
That's all well and good. But here's where it gets completely ablist, inaccessible and inconsiderate. The settings that control the port/LAG state is entirely images, and java-based clickable controls that don't actually respond to screen reader clickable identification/listing mechanisms. So if a port/LAG is part, not part, tagged, or untagged in a VLAN is only communicated as a visual signal in an image. And as we've seen in my previous post, even AI can't figure it out accurately more than half the time. Making adjustments to these controls is purely a guessing game.However, here's where my persistence, resourcefulness, and understanding of code comes in.
After slamming things around for a few hours, including my keyboard, I got the bright idea to start looking through the dev tools as well as page source.
It was then that I got frustrated once again, until I figured out that the VLAN membership stuff was in a separate iframe. So I had to look at its separate source specifically.
Once I found the code I needed, I then discovered that I could figure out what state each port/LAG was in by interpreting the html/java image code/tags and image names for each port. Two examples follow.
The first port is 10, and is removed from the VLAN. The second port is 11, and it is untagged in the VLAN.
<div class='portMember margin'><span class='portword'>10</span><div class='panels'><div class='portImage remImg'></div></div></div>
<div class='portMember margin'><span class='portword'>11</span><div class='panels'><div class='portImage untImg'></div></div></div>
So in the two above examples, we can see that the portword class is 10 and 11 respectively. This tells us what port we're dealing with.
Then later in the code, we can see that the portImage is either remImg or untImg. I've deduced that rem means remove, and unt means untagged.
So this is how I have to do VLANs in my $1,400 switch.
#Inaccessibility #Nonusability #Noninclusive #BadUX #BadUI #Ablism #RealEffects -
Ever found modern fancy scrollbars in #Firefox too accessible?
about:configand:widget.gtk.overlay-scrollbars.enabled → falsekeeps them fully visible while not however.
widget.non-native-theme.scrollbar.size.overridecan be used to make them THICC (I've set 512).
⸻ @mgorny
https://social.treehouse.systems/@mgorny/112751700910090648 -
Ever found modern fancy scrollbars in #Firefox too accessible?
about:configand:widget.gtk.overlay-scrollbars.enabled → falsekeeps them fully visible while not however.
widget.non-native-theme.scrollbar.size.overridecan be used to make them THICC (I've set 512).
⸻ @mgorny
https://social.treehouse.systems/@mgorny/112751700910090648 -
Ever found modern fancy scrollbars in #Firefox too accessible?
about:configand:widget.gtk.overlay-scrollbars.enabled → falsekeeps them fully visible while not however.
widget.non-native-theme.scrollbar.size.overridecan be used to make them THICC (I've set 512).
⸻ @mgorny
https://social.treehouse.systems/@mgorny/112751700910090648 -
Ever found modern fancy scrollbars in #Firefox too accessible?
about:configand:widget.gtk.overlay-scrollbars.enabled → falsekeeps them fully visible while not however.
widget.non-native-theme.scrollbar.size.overridecan be used to make them THICC (I've set 512).
⸻ @mgorny
https://social.treehouse.systems/@mgorny/112751700910090648 -
Ever found modern fancy scrollbars in #Firefox too accessible?
about:configand:widget.gtk.overlay-scrollbars.enabled → falsekeeps them fully visible while not however.
widget.non-native-theme.scrollbar.size.overridecan be used to make them THICC (I've set 512).
⸻ @mgorny
https://social.treehouse.systems/@mgorny/112751700910090648 -
CW: Medical insurance & accessibility
So they're apparently continuing to call & leave voicemails on my spouse's phone, even after he blocked their # & the codes come through too but as ridiculous as this remains, especially as in listening to a message - either they're leaving out 1/2 my last name or far less likely they're sort of mixing me up with another person so .... I'm planning on trying to visit one of their regional offices soon, to ask someone directly, if they'll stop these repeated unauthorized means of attempted communication & give a reasonable workaround for my inability to use telephone based communication.
By "reasonable" I mean that neither calling up 2 entities in replacement of giving the website a number for codes sent, as was passed along to me by the specialist as their "alternative"nor the likely one they'll offer which is demanding my hearing impaired & often speaking impaired spouse, be given full authorization to speak on my behalf, take any & all communications they want to do via telephone calls, continuing to use his # for those codes, in addition to his unblocking their number for said calls of theirs.🥴
-
CW: Medical insurance & accessibility
So they're apparently continuing to call & leave voicemails on my spouse's phone, even after he blocked their # & the codes come through too but as ridiculous as this remains, especially as in listening to a message - either they're leaving out 1/2 my last name or far less likely they're sort of mixing me up with another person so .... I'm planning on trying to visit one of their regional offices soon, to ask someone directly, if they'll stop these repeated unauthorized means of attempted communication & give a reasonable workaround for my inability to use telephone based communication.
By "reasonable" I mean that neither calling up 2 entities in replacement of giving the website a number for codes sent, as was passed along to me by the specialist as their "alternative"nor the likely one they'll offer which is demanding my hearing impaired & often speaking impaired spouse, be given full authorization to speak on my behalf, take any & all communications they want to do via telephone calls, continuing to use his # for those codes, in addition to his unblocking their number for said calls of theirs.🥴
-
CW: Medical insurance & accessibility
So they're apparently continuing to call & leave voicemails on my spouse's phone, even after he blocked their # & the codes come through too but as ridiculous as this remains, especially as in listening to a message - either they're leaving out 1/2 my last name or far less likely they're sort of mixing me up with another person so .... I'm planning on trying to visit one of their regional offices soon, to ask someone directly, if they'll stop these repeated unauthorized means of attempted communication & give a reasonable workaround for my inability to use telephone based communication.
By "reasonable" I mean that neither calling up 2 entities in replacement of giving the website a number for codes sent, as was passed along to me by the specialist as their "alternative"nor the likely one they'll offer which is demanding my hearing impaired & often speaking impaired spouse, be given full authorization to speak on my behalf, take any & all communications they want to do via telephone calls, continuing to use his # for those codes, in addition to his unblocking their number for said calls of theirs.🥴
-
CW: Medical insurance & accessibility
So they're apparently continuing to call & leave voicemails on my spouse's phone, even after he blocked their # & the codes come through too but as ridiculous as this remains, especially as in listening to a message - either they're leaving out 1/2 my last name or far less likely they're sort of mixing me up with another person so .... I'm planning on trying to visit one of their regional offices soon, to ask someone directly, if they'll stop these repeated unauthorized means of attempted communication & give a reasonable workaround for my inability to use telephone based communication.
By "reasonable" I mean that neither calling up 2 entities in replacement of giving the website a number for codes sent, as was passed along to me by the specialist as their "alternative"nor the likely one they'll offer which is demanding my hearing impaired & often speaking impaired spouse, be given full authorization to speak on my behalf, take any & all communications they want to do via telephone calls, continuing to use his # for those codes, in addition to his unblocking their number for said calls of theirs.🥴