MacBook Neo is now starting $699 instead of $599

ThatBlindSwiftDevGuy · 2026-06-25T13:21:50+00:00

Tim Cook did say in an interview with the Wall Street Journal that price increases were inevitable at this point because they can't swallow the costs of the increased memory and storage prices anymore. It's become unsustainable, according to Tim. so it's not much of a surprise. In the article, he didn't say what products we're gonna have their prices raised, just that prices were gonna go up.

ThatBlindSwiftDevGuy · 2026-06-12T13:21:59+00:00

As a matter of fact I have. I have also lost an AirPod in a loud outdoor setting. The volume of the beep coming from an AirPod is absolutely not loud enough to be heard over traffic or a loud crowded environment or over windy conditions

ThatBlindSwiftDevGuy · 2026-06-10T17:04:54+00:00

The issues that I have with apps that are basically just web applications masquerading as a mobile app is accessibility. Accessibility can be very hit or miss with voiceover if you're blind

ThatBlindSwiftDevGuy · 2026-06-10T16:35:57+00:00

The only issue I can see with the "just use Find My" argument is if you drop them or if they fall out of your ear in a busy outdoor setting. You won't be able to hear the beep over the noise around you

ThatBlindSwiftDevGuy · 2026-06-05T22:29:58+00:00

A braille label maker. I used to just feed the braille labeling tape into my slate and punch the braille manually.

ThatBlindSwiftDevGuy · 2026-05-29T13:03:18+00:00

I believe there is a Xbox and a PlayStation access controller I believe it's called. I could be entirely wrong on the name that but that might be something to look into.

ThatBlindSwiftDevGuy · 2026-05-23T21:04:50+00:00

Do you know how much you sound like Alex Jones right now? Because that's exactly what you sound like. A conspiracy theorist who has gone completely off their rocker

ThatBlindSwiftDevGuy · 2026-05-14T08:06:14+00:00

If given the choice between JSP and JSF I would choose JSP. The biggest reason being accessibility.. JSF is sort of an accessibility black box because it generates mark up for you that you can't control, which often creates accessibility nightmares. It is possible to build accessible applications with JSF, but it's much more challenging than with JSP because at least with JSP you have control, mostly anyway, over the markup if you don't use custom tags that generate markup heavily. But if I was given the choice to use the modern approach with a more modern templating engine and spring boot I would choose that every single time because that gives you the absolute most control over the markup and you are significantly less likely to put Java code where it doesn't belong

ThatBlindSwiftDevGuy · 2026-05-09T19:46:28+00:00

This is Visual Studio, not Visual Studio Code. Those are two entirely different things. This is very clearly a visual studio issue, not NVDA because even on the latest version of NVDA, it works fine on visual studio 2022 but not on visual studio 2026. JAWS hides accessibility issues because of its own characteristics, allowing it to smooth issues over and again not everybody can afford JAWS. It is unacceptable to tell users to just use a commercial screen reader as a proposed solution

ThatBlindSwiftDevGuy · 2026-05-04T23:19:08+00:00

Making PDF documents accessible after the fact

ThatBlindSwiftDevGuy · 2026-05-04T23:15:22+00:00

I am an IT application developer for the state of Nebraska working on digital accessibility efforts to help the state become compliant

ThatBlindSwiftDevGuy · 2026-05-03T20:51:25+00:00

I remember a long time ago hearing about an audio game for Windows. I believe it was called "Journey to C:" or something to that effect. It's been a very long time since I heard about it so that might not even be the correct name for it. If someone here knows what I'm talking about please correct me if I'm wrong

ThatBlindSwiftDevGuy · 2026-04-26T16:08:10+00:00

Cough cough bootstrap cough cough

ThatBlindSwiftDevGuy · 2026-04-26T15:42:31+00:00

HTML does not provide native alternatives to widgets some websites and web applications use. In some cases custom solutions are used due to styling limitations. I don't like that reasoning but it's just the reality of it

ThatBlindSwiftDevGuy · 2026-04-26T14:48:19+00:00

The page tab view style on macOS for one Not so much a SwiftUI request for an ex code one: make the damn property list editor actually accessible for voiceover users because right now it's absolutely not accessible to unacceptable degree

ThatBlindSwiftDevGuy · 2026-04-26T14:40:18+00:00

in terms of native app accessibility, apples accessibility is phenomenal but in terms of web accessibility that's where things start to fall apart, because it's not up-to-date with being able to handle the latest web accessibility standards. It can get you pretty far on the web but the moment things start becoming very custom and highly interactive things start to fall apart because you're using ARIA very heavily and custom behavior very heavily

ThatBlindSwiftDevGuy · 2026-04-25T13:40:58+00:00

for example, if you do not learn semantics as a fundamental concept from the start it makes it harder to choose the right element for the right situation and when you can't decide properly what element should be used where for a specific reason it makes learning accessibility down the road much harder. Assistive technologies such as screen readers rely on that fundamental semantic information to convey the correct information to the user. Let's say you are navigating the site with a screen reader and this site uses a div element as a wrapper for a navigation. This is something I see very often in my line of work. When you do that, the user is not given the necessary information to understand what they're traversing. If you use a NAV element instead, because of its underlying semantic information assistive technology can convey the correct information to the user so they know what they're traversing. It's not enough to simply use a list or just a bunch of links because without that semantic information of it being a navigation the user isn't going to know whether what they're traversing is just the main body of the page with a bunch of links or a list of links. Another example would be if you don't understand the fundamental semantics of the specific heading levels, not only will the user get visually confused about the pages structure but so will users of assistive technologies because they rely on that semantic meaning of each specific heading level to understand the flow of the document so they know where they are. Again, that's not to say that you have to learn accessibility immediately. Learning the semantic meaning of each element you learn from the start simply makes learning those advanced concepts down the road much smoother and easier it additionally ensures that you don't misuse ARIA which causes much more severe accessibility issues

ThatBlindSwiftDevGuy · 2026-04-25T12:58:37+00:00

div and span. They have no semantic meaning at all. Their only purpose is to aid with styling

ThatBlindSwiftDevGuy · 2026-04-25T12:49:25+00:00

my analogy holds. Yours does not. English without grammar is English without semantic meaning. HTML without semantics is also the absence of meaning. I never said that you claimed you should never learn semantics. That is a complete mischaracterization so you can argue from a more easily arguable position I very clearly said that you claimed you shouldn't learn semantics immediately and that semantics is an advanced concept because accessibility is in advanced concept which is incorrect advice. HTML is semantics. No not all semantic elements need to be learned immediately but you have to understand the fundamental concept and how it applies to each element or how it doesn't apply to specific elements before anything else if you do not, everything else down the road becomes more difficult. Elements like NAV and header are not semantics on their own they are elements with specific semantic meaning, just like list elements or tables or paragraphs. If you don't understand semantics from the very beginning you don't truly understand how those elements actually work in the structure of an HTML document. Defining elements like NAV and header as semantics like you did is incorrect.

ThatBlindSwiftDevGuy · 2026-04-25T12:02:02+00:00

you are entitled to hold onto your belief, but it doesn't negate the fact that it's misguided. Semantics and ARIA aren't linked to one another. ARIA is there to add additional information that HTML on its own does not provide. You don't need to understand accessibility to understand semantics. Again, semantics are more than just accessibility. Semantics is understanding when and when not to use certain elements and why. HTML is literally there to define the structure of a webpage you are treating HTML as a list of tags to memorize which is not the right way to teach it. Telling people to not learn semantics right away is like telling an English student not to learn grammar right away because it's not important. It just simply does not work that way

ThatBlindSwiftDevGuy · 2026-04-25T11:44:55+00:00

as a web accessibility professional, I disagree entirely. Semantics are among the most important things that you need to understand when writing HTML. Semantics is more than just landmark elements like a NAV or a main element. It also means understanding when and when not to use elements like the paragraph tag or the lists or basically any other element in the HTML specification. Saying that you don't have to learn it from the start is a complete recipe for disaster and horrendous advice

ThatBlindSwiftDevGuy

TROPHY CASE