Accessibility Specialist. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
Love the concept of this, but weird on iPhone as where you tap becomes white but I am sure that could be fiddled with.
I am not sure why I didn’t think of using a range slider. Guess what I am going to be fiddling with to see if I can take your concept and make it work perfectly!
P.S. the “thanks for reading” was a nice touch, made me chuckle
Accessibility Specialist. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
Accessibility Specialist. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
It’s more my thing that due to the fact that a lot of JAWS users still use IE.
Small projects I don’t bother apart from IE11, but anything with 1million plus turnover the extra work for IE9 and 10 pays for itself so it is worth it. Bear in mind I do more e-commerce than SAAS so the JS requirements are never horrendous!
Accessibility Specialist. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
I agree with the sentiment but I have no control over what some people use (due to lack of technical knowledge) or are forced to use (due to compatibility with screen reader technology) so while they are still in use I will always try to support them.
With that being said support vs perfection is a very different thing, as long as you can use it and get to the end goal it doesn't matter much if it looks weird etc.
I will be covering this in my (soon to be released) rebuttal piece!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Love the concept of this, but weird on iPhone as where you tap becomes white but I am sure that could be fiddled with.
I am not sure why I didn’t think of using a range slider. Guess what I am going to be fiddling with to see if I can take your concept and make it work perfectly!
P.S. the “thanks for reading” was a nice touch, made me chuckle
Yes, I updated the post with a small disclaimer!
I hatched up the idea this morning, and didn't test on iPhone - but will look into it soon.
OK, found the iPhone-issue. I had written
pacityinstead ofopacityfor the thumb. Beers on me.Glad you spotted it problem is indeed solved, I never even attempt to debug on my phone 😜🤣
As I said before the principle excites me and although IE support would be horrendous to implement this could well be a pattern that works well!
I need to get to the test bench next week and see if it behaves as well as I think it will!
I don’t do anything with IE-support anymore, but I guess a few clients still need it?
It’s more my thing that due to the fact that a lot of JAWS users still use IE.
Small projects I don’t bother apart from IE11, but anything with 1million plus turnover the extra work for IE9 and 10 pays for itself so it is worth it. Bear in mind I do more e-commerce than SAAS so the JS requirements are never horrendous!
Please no more IE. Let it die 🙏🏾. Let it be history please.
Amen!
I agree with the sentiment but I have no control over what some people use (due to lack of technical knowledge) or are forced to use (due to compatibility with screen reader technology) so while they are still in use I will always try to support them.
With that being said support vs perfection is a very different thing, as long as you can use it and get to the end goal it doesn't matter much if it looks weird etc.
I will be covering this in my (soon to be released) rebuttal piece!