In article <t53g51$rq2$1@gioia.aioe.org>, Andrew
<Andrew97d-junk@mybtinternet.com> wrote:
> I object to having to pay just to get *in* when there be nothing worth
> buying.

Well, I could say I object to paying to get into, say, a concert when I
didn't enjoy the music. Ditto for some museums, galleries, etc.

But the reality is that you have to pay to find out. Yes, it would be nice
if it were 'free', but bear TANSTAAFL in mind.

Personally, my interest would also be to see what is on show as it may help
me find out about items I didn't know existed, or details on items I didn't
know - even if I didn't buy anything.

Also, collect contact details - which of course the show-runners might want
me to not get without paying up as it means less need to pay again in
future.

> Maybe they should make sellers add a percentage onto their
> prices when they make a sale and pass this percentage to the organiser.
> Browsers and thwarted buyers then do not get fleeced just for attending.

Snag would be that 'policing' that would push up the costs.

It's your choice though. If you don't want to pay, don't go.They run on a
commercial basis.

Alas, I don't get the option as they don't have such events where I can
manage to reach them.

Jim

--
Please use the address on the audiomisc page if you wish to email me.
Electronics https://www.st-andrews.ac.uk/~www_pa/Scots_Guide/intro/electron.htm
biog http://jcgl.orpheusweb.co.uk/history/ups_and_downs.html
Audio Misc http://www.audiomisc.co.uk/index.html

Alas, most website builders use some form of software to 'build' pages
whilst having no clue what this produces in terms of page code. So build
what works for them or their main audience.

Things get worse as the range of 'devices' widens causing problems. e.g.
the difference between a small/narrow/verical FOV of a 'phone' compared
with a desktop computer using a big high-rez screen. This in itself causes
problems at times when people using site-building software that makes
incorrect assumptions or mistakes a desktop browser with a phone.

Only a small minority of website builders these days understand the page
code they generate... or even look at the actual code at all! If they did,
they'd often find it totally baffling.

So I'm afraid this is an issue which gets left to whoever writes the
software you use to try and make sense of the results. Who are they?

Jim

In article <t53nkm$dg1$1@dont-email.me>, Brian Gaff \(Sofa\)
<briang1@blueyonder.co.uk> wrote:
> Oh, I have no idea really, as its all down to the API the browser
> exposes to screenreaders I think. I'm not sure where to point you at,
> but I'm sure there are technical resources out there, but the multi
> layers of it are a bit beyond me. As long as they all behave we would
> not have to know as long as page authoring uses the correct accessible
> guidelines. Brian

--
Please use the address on the audiomisc page if you wish to email me.
Electronics https://www.st-andrews.ac.uk/~www_pa/Scots_Guide/intro/electron.htm
biog http://jcgl.orpheusweb.co.uk/history/ups_and_downs.html
Audio Misc http://www.audiomisc.co.uk/index.html