Adam MacLeod<p>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.<br>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.<br>So it turns out that practically the entire web UI is Java script. Surprised, anyone?<br>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?<br>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.</p><p>However, here's where my persistence, resourcefulness, and understanding of code comes in.<br>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.<br>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.<br>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.<br>The first port is 10, and is removed from the VLAN. The second port is 11, and it is untagged in the VLAN.<br>&lt;div class='portMember margin'&gt;&lt;span class='portword'&gt;10&lt;/span&gt;&lt;div class='panels'&gt;&lt;div class='portImage remImg'&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;<br>&lt;div class='portMember margin'&gt;&lt;span class='portword'&gt;11&lt;/span&gt;&lt;div class='panels'&gt;&lt;div class='portImage untImg'&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;<br>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.<br>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.<br>So this is how I have to do VLANs in my $1,400 switch.<br><a href="https://fedi.adamm.cc/tags/Inaccessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Inaccessibility</span></a> <a href="https://fedi.adamm.cc/tags/Nonusability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nonusability</span></a> <a href="https://fedi.adamm.cc/tags/Noninclusive" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Noninclusive</span></a> <a href="https://fedi.adamm.cc/tags/BadUX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BadUX</span></a> <a href="https://fedi.adamm.cc/tags/BadUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BadUI</span></a> <a href="https://fedi.adamm.cc/tags/Ablism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ablism</span></a> <a href="https://fedi.adamm.cc/tags/RealEffects" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RealEffects</span></a></p>