Chris TrottierI just embedded a search engine into a #Calckey post.
How did I do that?
By typing the following line into a post:
Calckey [search]
Take a look for yourselves here:
FeralRobots@atomicpoet It's neat but I don't like it.
1. If 'Calckey' is meant to be the label, that's a pattern with accessibility & usability problems.
2. Don't really understand the pattern (see prev) - looks like 'Calckey' is meant to be the label but it ends up the search term [placeholder]. Put another way, doesn't behave like other shortcode patterns
3. Expected behavior (which to me is 'search this site') doesn't match with actual behavior (which seems to be 'search default engine for this site').
1. If 'Calckey' is meant to be the label, that's a pattern with accessibility & usability problems.
2. Don't really understand the pattern (see prev) - looks like 'Calckey' is meant to be the label but it ends up the search term [placeholder]. Put another way, doesn't behave like other shortcode patterns
3. Expected behavior (which to me is 'search this site') doesn't match with actual behavior (which seems to be 'search default engine for this site').
@atomicpoet Ultimately I fall down in the 'we can but should we' camp on this. & as implemented, I'd say it shouldn't be used. Bad #a11y, bad #UX. URL with a GET string is better, because it tells the user what search engine they'll be using & can be labeled using the link text.