WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [WebAim] requesting for the recommendations from the experts

for

From: shankar shan
Date: Oct 17, 2016 10:12AM

hi rakesh and jamous bro, thanks for the quick response.

for my better understanding, I need some good css tutorials with the examples
I just gone through the w3schools, but, I was not satisfied about the tutorials.
they provided the tutorials, but not the techniques/methods for
implementing the css with html.

sorry, if I am wrong.








On 10/17/16, Maxability Accessibility for all
< <EMAIL REMOVED> > wrote:
> I second JP,
>
> The best tutorial I found was W3Schools. www.w3schools.com. People define
> it as a basic but until the basics are not strong it does not help building
> complex applications.
> 2. Use simple text editors such as notepad. Even today I do that to test
> simple code snippets.
> 3. Let the participants visualize the effect of CSS. The visual effect of
> each CSS property should be registered in the participants mind.
> 4. Using the all punctuation feature of screen reader possibility of
> missing syntax errors can be minimized.
>
> Hope this helps.
>
> Thanks & Regards
> Rakesh
> www.maxability.co.in
>
>
>
>
> On Mon, Oct 17, 2016 at 6:29 AM, JP Jamous < <EMAIL REMOVED> > wrote:
>
>> I come from the old school of programming. At least, I was taught by an
>> old programmer that I am still thankful to the knowledge I acquired
>> through
>> him.
>>
>> Use a notepad and type away. Have them understand proper semantic. Do not
>> get then relying on a RAD - Rapid Application Development.
>>
>> Once, they learn the basic well. You can explain to them Visual Studio or
>> any other IDE.
>>
>> My professor in college used to tell me, You know to know why it is doing
>> this? Output it to the screen. Do not use the immediate window or those
>> inaccessible tools in Visual Studio.
>>
>> When I started working out in the field, I found programmers older than me
>> that got lost if the immediate window did not show them how server-side
>> coding was causing a runtime error. Whereas, I had much less server-side
>> errors because I would run through the steps in my head at first. If
>> anything went bad, I would output to the screen the error and it loads on
>> the page. In fact, I solved so many issues to other sighted programmers
>> that way when I was using asp.net.
>>
>> Focus on proper semantic and use W3 tutorials. They will walk them step by
>> step through long and short hand markup. Make sure you explain each CSS
>> property in details and educate them how visually it would impact design.
>>
>> Once they have a strong foundation, they will be able to use any editor
>> they wish to use to make their development faster.
>>
>> Personally and from lots of experience in the field, I refuse using
>> editors to teach new students any type of language. In fact, I would ask
>> my
>> interns in the past to take a quick exam where they only have a piece of
>> paper and a pen to answer different coding questions. I would do that or
>> provide them with a machine that has nothing but notepad on it.
>>
>> Only that way, I was able to who what they were doing and who did not. The
>> corporate that I work at has developers that coded something like this
>> which I couldn't believe.
>>
>> <label role="radio" for="first-name">
>> Enter your first name:
>> <input type="radio" id="first-name" required />
>> </label
>>
>> They were so confused why screen readers were either announcing the
>> selected status twice or always stated the status as not selected.
>>
>>
>>